FHIR Profiles from other Organizations

FHIR can and is profiled by organizations other than HL7. This page captures these organizations and the profiles they have published.

The status of these specifications is the other Organizations responsibility.

Integrating the Healthcare Enterprise (IHE)

IHE publishes their profiles on http://www.ihe.net

IHE subset of Profile on FHR http://wiki.ihe.net/index.php/Category:FHIR

An IHE Profile is equivalent to a FHIR Implementation Guide. They take a specific use-case, define Actors, define Transactions, and define Options; From this a set of interoperability constraints are defined for each Actor within that Profile. These constraints can be coded as a FHIR Profile.

IT Infrastructure (ITI) domain

The IT Infrastructure profiles are published on the IHE Technical Framework web site and described on the IHE Wiki

• Mobile access to Health Documents (MHD) a profile on DocumentReference and DocumentManifest to provide a HTTP REST and Mobile application friendly API for the usecases profiled in XDS, XDR, and XCA. The MHD profile may be used as an API to these Document Sharing infrastructures, or may be used alone.
• Patient Demographics Query for Mobile (PDQm) a profile of the FHIR Patient resource for simple lookup and reference. Following the functionality requirements profiled in PDQ (HL7 v2), and PDQv3 (HL7 v3)
• Patient Identifier Cross-reference for Mobile (PIXm) an operation profile for retrieving just cross-referenced identifiers for a given patient
• RESTful Query to ATNA a profile on AuditEvent for query and reporting.
• Mobile Alert Communication Management (mACM) a profile on Communication for alert notifications
• Mobile Care Services Discovery (mCSD) provides a RESTful interface to discover Care Services: Organization, Location, Practitioner, and Health Services
• Mobile Cross-Enterprise Document Data Element Extraction (mXDE accesses data elements extracted from shared structured documents
• Non-patient File Sharing (NPFSm) provides a RESTful interface enable sharing of non-patient files such as clinical workflow definitions, domain policies, and stylesheets

Companion

• Internet User Authorization (IUA) a profile of OAuth for use with HTTP REST access

Patient Care Coordination (PCC) domain

Patient Care Coordination profiles are published on the IHE Technical Framework, and described on the IHE wiki.

• Clinical Mapping (CMAP) supports mapping to and from clinical terminologies
• Guideline Appropriate Ordering (GAO) Supplies a mechanism by which EHR and departmental systems can evaluate orders to determine whether these orders conform to guidelines.
• Reconciliation of Clinical Content and Care Providers (RECON) 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
• Dynamic Care Planing (DCP) Profile 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 shares information about a patient's care teams
• Query for Existing Data for Mobile (mQED) queries for clinical data elements, including observations, allergy and intolerances, conditions, diagnostic results, medications, immunizations, procedures, encounters and provenance

Radiology Imaging (RAD) domain

Radiology Imaging profiles are published on the IHE Technical Framework, and described on the IHE wiki.

• Mobile Access to Health Documents for Imaging (MHD-I)
• Standardized Operational Log of Events (SOLE) stores and retrieves logs of operational events (patient arrives, scan complete, etc)

Quality, Research, and Public Health (QRPH) domain

• Mobile Retrieve Form for Data Capture (mRFD) describes the exchange of context data to allow a seamless form launch with supporting clinical context
• Vital Records Death Reporting (VRDR) defines a Retrieve Form for Data Capture (RFD) 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