IHE ITI on FHIR

IHE ITI has a set of profiles on FHIR existing in Trial Implementation today. These were written against FHIR DSTU2. These have been updated to STU3, now in ballot for members of the ITI Technical Committee to comment and vote on.  Details and access to the ballot drafts of these documents is available from the ballot.

• Mobile access to Health Documents (MHD) 
• DocumentReference, DocumentManifest, List, Patient, Practitioner, Binary, OperationOutcome, Bundle
• Using FHIR FMM 1-5
• Also added some options to recognize XDS-on-FHIR
• Mobile Alert Communication Management (mACM)
• CommunicationRequest, Communication, OperationOutcome, Bundle
• Using FHIR FMM 2-5
• Patient Demographics Query for Mobile (PDQm)
• Patient, OperationOutcome, Bundle
• Using FHIR FMM 5
• Patient Identifier Cross-Reference for Mobile (PIXm)
• operations, Parameters, OperationOutcome, Bundle
• Using FHIR FMM 5
• Add RESTful Query to ATNA
• AuditEvent, OperationOutcome, Bundle
• Using FHIR FMM 3-5
• Appendix Z on HL7 FHIR
• Various reusable guidance and specification
• Mobile Security Considerations

The IHE ITI Technical Committee is also working on new profiles using FHIR. These will be further discussed in later articles.

• Mobile Care Services Discovery (mCSD)
• Including Healthcare Provider Directory (HPD) capability
• Organization, Location, Practitioner, PractitionerRole,  HealthcareServices, Binary, OperationOutcome, Bundle
• Non-Patient File Sharing (NPFS)
• Sharing and Management of Files that are not associated with a patient
• For example: Stylesheets, configuration, policy definitions, workflow definitions
• DocumentReference, Binary, OperationOutcome, Bundle
• Access to Document-extracted Data-elements (ADD) 
• Formerly: Patient Centric Element Location
• This is a profile that combines XDS/MHD and QEDm to describe how a Document Sharing environment can provide more fine grain access (Resource) to data shared as documents. 
• This profile does rely on creative systems engineering to decompose the documents into the FHIR resources. This might leverage CDA-on-FHIR, or some other methodology. This methodology is not specified.
• What is specified is that the fine grain details must have Provenance pointing at the Documents from which the data came. This enables a consumer to retrieve using XDS or MHD the document from which the fine grain details came from.

The IHE ITI and PCC are working jointly on one as well:

• Query or Existing Data for mobile (QEDm)
• supporting Resource level access such as allergies, problems, medications, etc
• Observation;  AllergyIntolerance;  Condition (Problem);  Procedure;  Encounter;  DiagnosticReport;  MedicationRequest;  MedicationStatement;  Medication;  Immunization
• Provenance, OperationOutcome, Bundle

IHE ITI is also working on one non FHIR Profile

• Remove Metadata and Document (RMD)
• This is a profile on XDS for administrative ability to remove metadata entries and remove documents

Lastly IHE Document Digital Signature (DSG) Profile approved for Final Text