This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Profiles from other Organizations"
Jump to navigation
Jump to search
JohnMoehrke (talk | contribs) |
JohnMoehrke (talk | contribs) |
||
| Line 29: | Line 29: | ||
Patient Care Coordination profiles are published on the [http://ihe.net/Technical_Frameworks/#pcc IHE Technical Framework], and described on the [http://wiki.ihe.net/index.php/Profiles#IHE_Patient_Care_Coordination_Profiles IHE wiki]. | Patient Care Coordination profiles are published on the [http://ihe.net/Technical_Frameworks/#pcc IHE Technical Framework], and described on the [http://wiki.ihe.net/index.php/Profiles#IHE_Patient_Care_Coordination_Profiles IHE wiki]. | ||
| − | * [http:// | + | * [http://wiki.ihe.net/index.php/Clinical_Mapping Clinical Mapping (CMAP)] supports mapping to and from clinical terminologies |
| − | * [http://www.ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_Suppl_GAO.pdf Guideline Appropriate Ordering (GAO)] Supplies a mechanism by which EHR and departmental systems can evaluate orders to determine whether these orders conform to guidelines. | + | * [http://www.ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_Suppl_GAO.pdf Guideline Appropriate Ordering (GAO)] Supplies a mechanism by which EHR and departmental systems can evaluate orders to determine whether these orders conform to guidelines. |
| − | * [http:// | + | * [http://wiki.ihe.net/index.php/Reconciliation_of_Clinical_Content_and_Care_Providers 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 |
| − | * [http://ihe.net/ | + | * [http://wiki.ihe.net/index.php/Dynamic_Care_Planning 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. |
| + | * [http://wiki.ihe.net/index.php/Dynamic_Care_Team_Management Dynamic Care Team Management] shares information about a patient's care teams | ||
| + | * [http://wiki.ihe.net/index.php/Query_for_Existing_Data_for_Mobile 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 (RAD) domain == | ||
Revision as of 17:49, 28 August 2017
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.
Contents
Integrating the Healthcare Enterprise (IHE)
IHE publishes their profiles on http://www.ihe.net
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) - Published 2014-05-30
