Here are the IHE profiles that leverage FHIR today...
- IT Infrastructure
- Add RESTful Query to ATNA - where a query on FHIR AuditEvent interrogates all of the audit log recorded in Audit Trail and Node Authentication Audit Repository
- Internet User Authorization - defines a plugable basic OAuth interaction to enable app and user authorization. Intended to be enhanced based on use-case analysis.
- Mobile access to Health Documents (MHD) - defines a FHIR interface to an XDS/XCA environment, in a way that can also be used standalone. Degenerate form is equivalent to Argonaut document access.
- Mobile Alert Communication Management(mACM) - defines a way to send short unstructured text alerts to a human using CommunicationRequest resource
- Mobile Care Services Discovery (mCSD) (including HPD) - defines a comprehensive Provider Directory including Organization, Location, Services, and Practitioners.
- Mobile Cross-Enterprise Document Data Element Extraction - defines a method of access to data element level data (FHIR) given shared documents (XDS)
- Non-patient File Sharing (NPFSm) - defines a method of managing and publishing non-patient files like style-sheets, policy, and configurations
- Patient Demographics Query for Mobile (PDQm) - defines equivalent functionality to PDQ, simple query on Patient resource
- Patient Identifier Cross-Reference for Mobile (PIXm) - defines equivalent functionality to PIX, operation to request patient identifiers given only an identifier.
- Query for Existing Data for Mobile (QEDm) - supports queries for clinical data elements, including observations, allergy and intolerances, conditions, diagnostic results, medications, immunizations, procedures, encounters and provenance by making the information widely available to other systems within and across enterprises.
- Clinical Mapping (CMAP) - supports the need of systems to translate codes from one terminology to another to support exchange of information between different systems.
- Dynamic Care Planning (DCP) - provides the structures and transactions for care planning, sharing Care Plans that meet the needs of many, such as providers, patients and payers.
- Dynamic Care Team Management (DCTM) - provides the means for sharing care team information about a patient’s care teams that meet the needs of many users, such as providers, patients and payers
- Reconciliation of Clinical Content and Care Providers (RECON) - profile provides the ability to communicate lists of clinical data that were reconciled, when they were reconciled and who did the reconciliation using CDA® constructs and FHIR® Resource attributes.
- Point-of-Care Medical Device Tracking (PMDT) - provides definition for a mobile Device.
- Remote Patient Monitoring (RPM) - provides means of reporting measurements taken by Personal Healthcare Devices in a remote location
- Routine Interfacility Patient Transport (RIPT) - provides means of updating a Transport team with critical and necessary medical information on a patient to be transported
- Standardized Operational Log of Events (SOLE) - uses AuditEvent to record business events so that business intelligence have quality data to analyze.
- Uniform Barcode Processing (UBP) - describes a way to send the information contained in a barcode and in return receive the parsed content of that barcode in the form of a FHIR resource instance - a medication, a device, a patient, or staff.
- Mobile Medication Administration (MMA) - defines the integration between healthcare systems and mobile (or any other) clients using RESTful web services. This allows connecting EHRs with smartphones, smart pill boxes, and other personal or professional devices.
- Mobile Retrieve Form for Data Capture (mRFD) - provides a method for gathering data within a user's current application to meet the requirements of an external system
- Vital Records Death Reporting (VRDR) - defines a mRFD content profile that will specify derivation of source content from a medical summary document. by defining requirements for form filler content and form manager handling of the content.:
I have succeeded to get the IHE Profiles listed on the FHIR.org registry of Implementation Guides. This is a manual step today, but will likely continue to be a manual step to assure that what gets published has passed the IHE Governance for being listed.
See my other articles on FHIR