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) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
= Integrating the Healthcare Enterprise (IHE) = | = Integrating the Healthcare Enterprise (IHE) = | ||
IHE publishes their profiles on http://www.ihe.net | 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. | 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. | ||
| Line 12: | Line 14: | ||
The IT Infrastructure profiles are published on the [http://ihe.net/Technical_Frameworks/#IT IHE Technical Framework web site] and described on the [http://wiki.ihe.net/index.php/Profiles#IHE_IT_Infrastructure_Profiles IHE Wiki] | The IT Infrastructure profiles are published on the [http://ihe.net/Technical_Frameworks/#IT IHE Technical Framework web site] and described on the [http://wiki.ihe.net/index.php/Profiles#IHE_IT_Infrastructure_Profiles IHE Wiki] | ||
| − | * [http://wiki.ihe.net/index.php | + | * [http://wiki.ihe.net/index.php/Mobile_access_to_Health_Documents 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. |
| − | * [http:// | + | * [http://wiki.ihe.net/index.php/Patient_Demographics_Query_for_Mobile_(PDQm) 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) |
| − | * [http://wiki.ihe.net/index.php | + | * [http://wiki.ihe.net/index.php/Patient_Identifier_Cross-Reference_for_Mobile_(PIXm) Patient Identifier Cross-reference for Mobile (PIXm)] an operation profile for retrieving just cross-referenced identifiers for a given patient |
| − | * [http:// | + | * [http://wiki.ihe.net/index.php/Audit_Trail_and_Node_Authentication RESTful Query to ATNA] a profile on AuditEvent for query and reporting. |
| − | * [http:// | + | * [http://wiki.ihe.net/index.php/Mobile_Alert_Communication_Management(mACM) Mobile Alert Communication Management (mACM)] a profile on Communication for alert notifications |
| + | * [http://wiki.ihe.net/index.php/Mobile_Care_Services_Discovery_(mCSD) Mobile Care Services Discovery (mCSD)] provides a RESTful interface to discover Care Services: Organization, Location, Practitioner, and Health Services | ||
| + | * [http://wiki.ihe.net/index.php/Mobile_Cross-Enterprise_Document_Data_Element_Extraction Mobile Cross-Enterprise Document Data Element Extraction (mXDE] accesses data elements extracted from shared structured documents | ||
| + | * [http://wiki.ihe.net/index.php/Non-patient_File_Sharing_(NPFSm) 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 | Companion | ||
| − | * [http:// | + | * [http://wiki.ihe.net/index.php/Internet_User_Authorization Internet User Authorization (IUA)] a profile of OAuth for use with HTTP REST access |
== Patient Care Coordination (PCC) domain == | == Patient Care Coordination (PCC) domain == | ||
| Line 25: | Line 31: | ||
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 Planning] (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 | ||
| + | * [http://wiki.ihe.net/index.php/Point-of-Care_Medical_Device_Tracking Point-of-Care Medical Device Tracking] coses the loop on data acquisition at the point-of-care in support of reporting data about implantable medical devices and medical devices during a procedure | ||
| + | |||
| + | == Radiology Imaging (RAD) domain == | ||
| + | |||
| + | Radiology Imaging profiles are published on the [http://ihe.net/Technical_Frameworks/#rad IHE Technical Framework], and described on the [http://wiki.ihe.net/index.php/Profiles#IHE_Radiology_Profiles IHE wiki]. | ||
| + | |||
| + | * [http://www.ihe.net/uploadedFiles/Documents/Radiology/IHE_RAD_Suppl_MHDI.pdf Mobile Access to Health Documents for Imaging (MHD-I)] | ||
| + | * [http://wiki.ihe.net/index.php/Standardized_Operational_Log_of_Events 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 == | ||
| + | |||
| + | * [http://wiki.ihe.net/index.php/Mobile_Retrieve_Form_for_Data_Capture Mobile Retrieve Form for Data Capture (mRFD)] describes the exchange of context data to allow a seamless form launch with supporting clinical context | ||
| + | * [http://wiki.ihe.net/index.php/Vital_Records_Death_Reporting 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 | ||
| + | |||
| + | == Pharmacy domain == | ||
| + | |||
| + | In Public Comment | ||
| + | |||
| + | * [http://wiki.ihe.net/index.php/Mobile_Medication_Administration Mobile Medication Administration (MMA)] connects EHR with devices such as smartphones and smart pill boxes using RESTful web services | ||
| + | * [http://wiki.ihe.net/index.php/Uniform_Barcode_Processing Uniform Barcode Processing] | ||
Revision as of 16:37, 27 October 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
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 Planning (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
- Point-of-Care Medical Device Tracking coses the loop on data acquisition at the point-of-care in support of reporting data about implantable medical devices and medical devices during a procedure
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
Pharmacy domain
In Public Comment
- Mobile Medication Administration (MMA) connects EHR with devices such as smartphones and smart pill boxes using RESTful web services
- Uniform Barcode Processing
