Difference between revisions of "Multiple Content Views"

From IHE Wiki
Jump to: navigation, search
(Created page with "''This template is for the one or two page user-oriented overview of an IHE Profile that is in Final Text, Trial Implementation or perhaps Public Comment. Delete text in ital...")
 
(See Also)
 
(13 intermediate revisions by 2 users not shown)
Line 1: Line 1:
''This template is for the one or two page user-oriented overview of an IHE Profile that is in Final Text, Trial Implementation or perhaps Public Comment.  Delete text in italics and replace it with your material.  Don't forget to delete the double quotes too.''
+
The Multiple Content Views profile provides guidance on how text in CDA documents may be tagged to achieve different rendering behaviors.
 
+
''Your page name should simply be Full Profile Name with spaces, with capitals, without the acronym. e.g. Scheduled Workflow. so it provides a title to the page. You can redirect the acronym to the full named page if you like for bonus points.''
+
 
+
 
+
''<IN ONE LINE, tell a user what the profile is about (including the acronym) so they can decide if they're on the right page.  Basically this should be the same sentence that appears on the [[Profiles]] catalog page>''
+
 
+
''e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.''
+
  
 
__TOC__
 
__TOC__
  
 
==Summary==
 
==Summary==
''<Describe the profile in about a paragraph using user-oriented language.  Focus on what it accomplishes for a user (i.e. the Use Cases).  Don't get into how it works, leave that to the Details section.>''
+
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.
 
+
''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about.  Do not use an actor/transaction diagram here.  Show your graphic to someone for 5 seconds (literally) and ask them what it's about.  If what they say hits the main points in your summary paragraph, you have succeeded.  E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them. .>''
+
  
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
+
[[Image:MCVActorTransactions.png|350px]]
  
 
==Benefits==
 
==Benefits==
''<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler).  Consider using a bullet list for readability. Such benefits help users and vendors make the business case for the profile.  If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>''
+
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==
 
==Details==
  
''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+
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.
  
''<If the user might be familiar with the mechanisms used by the profile, you can mention them here.  E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>''
+
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.
  
''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short.  E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
 
 
 
==Systems Affected==
 
==Systems Affected==
''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>''
+
* EHR systems may format documents and display formatted documents
 
+
* PHR systems may display formatted documents
<!--
+
* ''PACS systems may store, manage, and/or display Evidence Documents.''
+
* ''Display systems may query, retrieve and display Evidence Documents.''
+
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
+
-->
+
  
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
  
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+
* [[Content Creator]]
 +
* [[Content Consumer]]
 +
 
 +
[[Image:MCVActorTransactions2.png|450px]]
  
 
==Specification==
 
==Specification==
  
'''Profile Status:''' [[Comments| Final Text]]   
+
'''Profile Status:''' [[Comments| Trial Implementation]]   
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
+
  
 
'''Documents:'''  
 
'''Documents:'''  
Line 68: Line 54:
  
 
==See Also==
 
==See Also==
 
''<The following sections can be left out if there is nothing to point to.  This is just to show where such information can go.>''
 
  
  
 
'''Related Profiles'''
 
'''Related Profiles'''
 
''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one.  Start with the name of the other profile as a link and then explain the relationship.>''
 
  
 
<!--
 
<!--
Line 86: Line 68:
 
'''Consumer Information'''
 
'''Consumer Information'''
  
The [[Profile FAQ Template]] answers typical questions about what the Profile does.  ''<Replace the link with a link to the actual FAQ page for the Profile>''
 
 
The [[Profile Purchasing Template]] describes considerations when purchasing equipment to deploy this Profile.  ''<Replace the link with a link to the actual Purchasing page for the Profile>''
 
  
 
'''Implementer Information'''
 
'''Implementer Information'''
  
The [[Profile Implementation Template]] provides additional information about implementing this Profile in software.  ''<Replace the link with a link to the actual Implementation page for the Profile>''
 
  
 
'''Reference Articles'''
 
'''Reference Articles'''
  
''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis).  Go ahead, Google: IHE <Profile Name> abstract  or Google: IHE <Profile Name> and under the "more" select "Scholar".  You might be surprised. >''
+
 
  
  
Line 102: Line 80:
 
This page is based on the [[Profile Overview Template]]
 
This page is based on the [[Profile Overview Template]]
  
[[Category:Template]]
+
[[Category:Profiles]][[Category:Patient Care Coordination]][[Category:CDA]][[Category:DocShare]]

Latest revision as of 10:00, 4 November 2019

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