Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Patient Data for your App

173 views

Published on

Accessing the patient data you need to provide a compelling healthcare app

Published in: Software
  • Be the first to comment

  • Be the first to like this

Patient Data for your App

  1. 1. Data for your App Accessing the patient data you need to provide a compelling healthcare app Ken Stevens, VP Healthcare, Intelliware Development 20 Apr 2017 www.appsforhealth.ca #appsforhealth
  2. 2. Question I’m setting out to answer You have a prototype for an innovative healthcare app. What kind of interoperability capabilities will it need to have in order for you to sell it in the Ontario Market? www.appsforhealth.ca
  3. 3. Standards Advice  Avoid HL7v3.  FHIR interfaces will be replacing it. (Exception: Rx)  Avoid level 3 CDA.  It is the cornerstone interoperability standard in the U.S.  But it doesn’t work  HL7v2 will be here for decades.  If you integrate with a hospital, you will be using HL7v2. Write once, run once.  SMART on FHIR is the future. But the future isn’t here yet.  Legacy systems will take at least 10 years to update www.appsforhealth.ca
  4. 4. Single-Sign On  OneId uses SAML. To operate in Ontario, you will likely need to use this.  The future is OpenID Connect. Don’t be surprised to see an OpenID Connect interface made available to OneID within the next couple of years. www.appsforhealth.ca
  5. 5. Access to Patient Data  Today only way is through a HIC (Health Information Custodian)  E.g. Hospital, Pharmacy, Long-term Care Home, Lab, Health Clinic  They will need to be your “sponsor.” You will need your sponsor to give you access to vendor who runs the system they run that holds patient data.  Existing HIC software vendors charge outrageous feeds to make even the simplest integration configurations. Their pricing models are generally connection based and can run from tens of thousands to millions of dollars. www.appsforhealth.ca
  6. 6. ITAC Health Information Technology Association of Canada Ken Stevens, Co-chair Interoperability and Standards Committee 20 Apr 2017 www.appsforhealth.ca #appsforhealth
  7. 7. ITAC Health Position on Canadian Healthcare Interoperability Standards www.appsforhealth.ca #appsforhealth 1. Standards should be the same across Canada. 2. Prefer standards that are commercially established internationally, esp. the U.S. 3. Phase out use of HL7v3, Promote adoption of IHE/XDS and FHIR. 4. Mandate interoperability standards compliance in RFPs. Enforce via conformance testing.
  8. 8. Benefits 1. Increase the number of solutions available for provinces. 2. Lower the cost to customize solutions for each province. 3. Expand the export market for innovative Canadian healthcare solutions. www.appsforhealth.ca #appsforhealth

×