Difference between revisions of "Medical Summaries Profile"

From IHE Wiki
Jump to navigation Jump to search
 
Line 1: Line 1:
#REDIRECT [[Medical Summaries Implementation]]
+
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.
 +
 
 +
 
 +
__TOC__
 +
 
 +
 
 +
==Summary==
 +
 
 +
The ''Cross-Enterprise Sharing of Medical Summaries'' profile provides a mechanism to automate the sharing process between care providers of Medical Summaries, a class of clinical documents that contain the most relevant portions of information about the patient intended for a specific provider or a broad range of potential providers in different settings. Medical Summaries are commonly created and consumed by electronic medical record systems at points in time of transfers of care such as referrals or discharge.
 +
 
 +
[[image:xdsms.png]]
 +
 
 +
==Benefits==
 +
 
 +
==Details==
 +
 
 +
The basic process flow supported by XDS-MS mirrors current manual practices: someone
 +
gathers the appropriate documents from the patient medical record, copies them, packages them
 +
up with a cover letter explaining the reason the information is being sent, and then ships the
 +
package to the receiving provider. This is often accompanied by a telephone call from the
 +
sending provider to the receiving provider that indicates that such information is forthcoming.
 +
 
 +
==Systems Affected==
 +
EHR Systems
 +
 
 +
==Actors==
 +
* [[Content Creator]]
 +
* [[Content Consumer]]
 +
 
 +
==Transactions==
 +
 
 +
==See Also==
 +
Profile Status: [[Comments| Final Text]]
 +
The [[Frameworks#IHE Patient Care Coordination Framework| Patient Care Coordination Framework]] is the official master document for this Profile.
 +
 
 +
The [[XDS-MS FAQ Template]] answers typical questions about what the Profile does.
 +
 
 +
The [[XDS-MS Purchasing Template]] describes considerations when purchasing equipment to deploy this Profile.
 +
 
 +
The [[XDS-MS Implementation Template]] provides additional information about implementing this Profile in software.
 +
 
 +
This page is based on the [[Profile Template]]
 +
 
 +
[[Category:Profiles]]

Revision as of 11:58, 22 November 2006

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.



Summary

The Cross-Enterprise Sharing of Medical Summaries profile provides a mechanism to automate the sharing process between care providers of Medical Summaries, a class of clinical documents that contain the most relevant portions of information about the patient intended for a specific provider or a broad range of potential providers in different settings. Medical Summaries are commonly created and consumed by electronic medical record systems at points in time of transfers of care such as referrals or discharge.

Xdsms.png

Benefits

Details

The basic process flow supported by XDS-MS mirrors current manual practices: someone gathers the appropriate documents from the patient medical record, copies them, packages them up with a cover letter explaining the reason the information is being sent, and then ships the package to the receiving provider. This is often accompanied by a telephone call from the sending provider to the receiving provider that indicates that such information is forthcoming.

Systems Affected

EHR Systems

Actors

Transactions

See Also

Profile Status: Final Text The Patient Care Coordination Framework is the official master document for this Profile.

The XDS-MS FAQ Template answers typical questions about what the Profile does.

The XDS-MS Purchasing Template describes considerations when purchasing equipment to deploy this Profile.

The XDS-MS Implementation Template provides additional information about implementing this Profile in software.

This page is based on the Profile Template