Multiple Content Views

From IHE Wiki
Jump to: navigation, search

The Multiple Content Views profile provides guidance on how text in CDA documents may be tagged to achieve different rendering behaviors.

Summary

The Multiple Content Views profile guidance on how text in CDA documents may be tagged to achieve different rendering behaviors allows one document to serve different needs based upon the requirements of the person viewing the document. For example, the viewing requirements of a patient differ from the requirements of a healthcare provider. The profile identifies many of the requirements expressed by patients, classifies these requirements, identifies the rendering behavior associated with each, and provides guidance on how to tag CDA content in order to bind it to an identified behavior. Use of this profile allows one CDA document to serve the needs of different Document Consumers.

MCVActorTransactions.png

Benefits

The profile allows one CDA document to serve the needs of different Document Consumers by providing the ability for one document to serve different needs based upon the requirements of the person viewing the document. For example, the viewing requirements of a patient differ from the requirements of a healthcare provider. The profile identifies many of the requirements expressed by patients, classifies these requirements, identifies the rendering behavior associated with each, and provides guidance on how to tag CDA content in order to bind it to an identified behavior.

Details

CDA documents contain data and details based upon various profiles and implementation guides. Representation and rendering of this data changes based upon different needs and audiences. Patients, providers and even systems each have different requirements for the content and rendering of the content in exported documents.

Various end users viewing CDA content are interested in specific portions of the available content and may not have immediate need to access other portions of the content. In order to streamline their workflows, there is a desire to be able to semantically identify narrative content in such a way as to allow customized user views to be implemented systematically between systems producing and consuming documents.

Systems Affected

  • EHR systems may format documents and display formatted documents
  • PHR systems may display formatted documents

Actors & Transactions:

MCVActorTransactions2.png

Specification

Profile Status: Trial Implementation

Documents:

<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>


Underlying Standards:


<list all the standards on which the profile is based; if possible with links to sources>

See Also

Related Profiles


Consumer Information


Implementer Information


Reference Articles



This page is based on the Profile Overview Template