Difference between revisions of "Retrieve Information for Display"
m (→Benefits) |
|||
| Line 9: | Line 9: | ||
'''Simple rendering of patient information''' | '''Simple rendering of patient information''' | ||
| − | * the Information Source is solely responsible to turn the healthcare specific semantics into what this IHE | + | * the Information Source is solely responsible to turn the healthcare specific semantics into what this IHE Integration Profile calls a “presentation” format. As a consequence the Display actor may process and render this “presentation” format with only generic healthcare semantics knowledge. |
| − | |||
| − | Integration Profile calls a “presentation” format. As a consequence the Display actor may process and render this | ||
| − | |||
| − | “presentation” format with only generic healthcare semantics knowledge. | ||
==Details== | ==Details== | ||
Revision as of 15:07, 1 April 2008
Summary
The Retrieve Information for Display (RID) Integration Profile provides simple and rapid read-only access to patient-centric clinical information that is located outside the user’s current application but is important for better patient care (for example, access to lab reports from radiology department). It supports access to existing persistent documents in well-known presentation formats such as CDA (Level 1), PDF, JPEG, etc. It also supports access to specific key patient-centric information such as allergies, current medications, summary of reports, etc. for presentation to a clinician. It complements workflows with access from within the users’ on-screen workspace or application to a broad range of information.
Benefits
Simple rendering of patient information
- the Information Source is solely responsible to turn the healthcare specific semantics into what this IHE Integration Profile calls a “presentation” format. As a consequence the Display actor may process and render this “presentation” format with only generic healthcare semantics knowledge.
Details
The Retrieve Information for Display (RID) Integration Profile:
- Offers the capability to leverage industry standards that address both the structure and content of documents
that may be returned by information sources. Where this profile references HL7 Clinical Documentation Architecture
(CDA), it limits itself to the approved CDA Level 1. Furthermore, it only uses a subset of CDA Level 1 that
facilitates making information available for display.
Systems Affected
Systems involved in this profile are:
- Enterprise-wide information systems that manage patient registration and services ordering (i.e.,
admit-discharge-transfer (ADT)/registration system and hospital information system (HIS ))
Actors & Transactions:
Specification
Profile Status: Final Text
Documents: IHE IT Infrastructure Technical Framework:
Underlying Standards:
See Also
Related Profiles
This page is based on the Profile Template
Status: Final Text
Current: IT Infrastructure Technical Framework.