The Standard

A report from the HL7 Da Vinci Project describes how two pioneering organizations demonstrated the real-world practicality and value of applying standard application program interfaces (APIs) to streamline the prior authorization process.

Regence, a payer based in the Pacific Northwest, and MultiCare Health System, a provider based in Washington state, spent about a year testing and fine-tuning processes that leverage HL7’s Fast Healthcare Interoperability Resources (FHIR^®) standard for APIs.

In addition, dozens of other organizations have tested FHIR APIs at more than 15 Connectathon testing events.

Seqster has developed a platform that allows patients and their caregivers to collect, visualize, manage and share all of their health data in one app. We aggregate clinical data points across providers chronologically using the industry-standard coding systems that the HL7 community knows all too well. 

 The HL7® FHIR® Connectathon Consumer Centered Data Exchange Track

Covered entities face an ever-growing demand to enable digital health apps to access Protected Health Information (PHI). The technical and legal requirements to enable this are the focus areas for the Consumer Centered Data Exchange (CCDE) track at the HL7 FHIR Connectathon. This track initiated at the San Diego Connectathon (September 2017), and it made more progress recently (January 27-28) at the New Orleans Connectathon. Track participation may have been piqued by Apple’s recent announcement that it will provide patients an “effortless solution bringing health records to iPhone”, and that Apple will use FHIR services to enable this.

Caption: Participants at the HL7 FHIR Connectathon 17 in New Orleans, LA. Image credit: Kai Heitmann.

Apple’s announcement couldn’t be more closely tied to the work of the enthusiastic CCDE track participants, representing the entire healthcare industry including providers, payers, government, academia and app developers. Apple could benefit a lot from this track’s work if iPhone users are to access PHI from covered entities beyond the initial 12 participants of the iOS 11.3 beta.

Why? Mainly because the CCDE track focuses on 3 key requirements:

1. It should be technically simple for a covered entity to verify that an app requesting access to a patient’s PHI is indeed controlled by that particular patient;
2. The way an app accesses PHI should be compliant with data governance and privacy policies of the covered entity, as well as HIPAA guidelines, and;
3. The experience of an app user should be simple enough so that they clearly understand and acknowledge what they are sharing with the app.