Difference between revisions of "Profiles"
Line 28: | Line 28: | ||
==[[Patient Care Coordination| IHE Patient Care Coordination]] Profiles== | ==[[Patient Care Coordination| IHE Patient Care Coordination]] Profiles== | ||
+ | === Final Text === | ||
+ | * [MS] [[Medical Summaries]] [http://www.ihe.net/technical_framework/upload/ihe_pcc_tf_rev1.1_ti_2006-06-20.pdf pdf] | ||
+ | This profile defines the content sections for Discharge Summaries and Referral Notes. It uses HL7 Clinical Document Architecture (CDA) Release 2 and Care Record Summary as its base standard and constrains this to level 3 encoding for medications, allergies and problem lists. | ||
+ | |||
+ | === Trial Implementation === | ||
+ | * [XPHR] [[Exchange of Patient Health Record Data]] [http://www.ihe.net/Technical_Framework/upload/IHE_PCC_TF_XPHR_Exchanging_PHR_Content_20060812.pdf pdf] | ||
+ | This profile describes the content and format of summary information extracted from a phr system for import into an ehr system, and visa versa. The purpose of this profile is to support interoperability between phr systems used by patients and ehr systems used by healthcare providers. | ||
+ | |||
+ | * [EDR] [[Emergency Department Referral]] [http://www.ihe.net/Technical_Framework/upload/IHE_PCC_TF_EDR_ED_Referral_PC_20060812.pdf pdf] | ||
+ | This profile allows clinicians to create electronic referrals to the emergency room including the nature of the current problem, past medical history, and medications. Upon arrival of the patient to the Emergency Department, the patient is identified as a referral, and the transfer document is incorporated into the EDIS. This profile builds onmedical summary adding structures to pass data specific for ed referral such as estimated time of arrival and transport method. | ||
+ | |||
+ | * [BPPC] [[Basic Patient Privacy Consent]] [http://www.ihe.net/Technical_Framework/upload/IHE_PCC_TF_BPPC_Basic_Patient_Privacy_Consents_20060810.pdf pdf] | ||
+ | This profile allows affinity domains to create a vocabulary of codes that identify policies with respect to information sharing. Each policy should identify which functional roles may access a document. | ||
+ | |||
+ | * [PPHP] [[Preprocedural History and Physical]][http://www.ihe.net/Technical_Framework/upload/IHE_PCC_TF_PPHP_Preprocedure_History_and_Physical_TI_2006_08_15.pdf pdf] | ||
+ | This profile allows clincians to prepare an electronic representation of a Preprocedural History and Physicial document. It is similar to a Medical Summary document and shares methods for conveying structured data for medications, allergies and problem, but additionally provides mechanisms to represent more specific detail needed for preprocedural care. | ||
==[[Patient Care Devices| IHE Patient Care Devices]] Profiles== | ==[[Patient Care Devices| IHE Patient Care Devices]] Profiles== |
Revision as of 16:03, 10 November 2006
IHE Integration Profiles describe a specific integration problem, and document the equipment roles, standards and design details for vendors to implement products that cooperate to address that problem. Integration Profiles offer a convenient way for vendors and users to reference the functionality defined in the IHE Technical Framework without having to restate all of the detail regarding IHE actors and transactions. For convenient reference, each Profile has a short acronym.
Each domain manages a collection of Profiles shown below. Alternatively, there is an alphabetized index of Profiles.
IHE Radiology Profiles
- [SWF] - Scheduled Workflow integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.
- [PIR] - Patient Information Reconciliation coordinates reconciliation of the patient record when images are acquired for unidentified (e.g. trauma), or misidentified patients.
- [CPI] - Consistent Presentation of Images maintains consistent intensity and image transformations between different hardcopy and softcopy devices.
- [XDS-I] - Cross-enterprise Document Sharing for Imaging supports sharing DICOM images, diagnostic reports and related information across a network of care sites.
- [TCE] - Teaching File and Clinical Trial Export lets users flag DICOM images and related information for automatic routing to teaching file authoring or clinical trials management systems.
- ...
IHE Cardiology Profiles
- [CATH] - Cardiac Cath Workflow ...
- [ECHO] - Echocardiography Workflow ...
- ...
IHE IT Infrastructure Profiles
IHE Laboratory Profiles
IHE Patient Care Coordination Profiles
Final Text
- [MS] Medical Summaries pdf
This profile defines the content sections for Discharge Summaries and Referral Notes. It uses HL7 Clinical Document Architecture (CDA) Release 2 and Care Record Summary as its base standard and constrains this to level 3 encoding for medications, allergies and problem lists.
Trial Implementation
This profile describes the content and format of summary information extracted from a phr system for import into an ehr system, and visa versa. The purpose of this profile is to support interoperability between phr systems used by patients and ehr systems used by healthcare providers.
This profile allows clinicians to create electronic referrals to the emergency room including the nature of the current problem, past medical history, and medications. Upon arrival of the patient to the Emergency Department, the patient is identified as a referral, and the transfer document is incorporated into the EDIS. This profile builds onmedical summary adding structures to pass data specific for ed referral such as estimated time of arrival and transport method.
- [BPPC] Basic Patient Privacy Consent pdf
This profile allows affinity domains to create a vocabulary of codes that identify policies with respect to information sharing. Each policy should identify which functional roles may access a document.
This profile allows clincians to prepare an electronic representation of a Preprocedural History and Physicial document. It is similar to a Medical Summary document and shares methods for conveying structured data for medications, allergies and problem, but additionally provides mechanisms to represent more specific detail needed for preprocedural care.