Difference between revisions of "CDA Document Summary Sections Profile"

From IHE Wiki
Jump to navigation Jump to search
 
(19 intermediate revisions by 2 users not shown)
Line 5: Line 5:
 
==Summary==
 
==Summary==
 
The CDA document summary sections can be created by summarizing pertinent information. The data that goes in the summary sections can be user defined or can be based on specified use cases provided by the profile. The CDA document summary sections can be rendered for viewing. Content in some CDA document summary sections can be imported when possible (i.e.contains discrete entries) by the consuming system if desired.  
 
The CDA document summary sections can be created by summarizing pertinent information. The data that goes in the summary sections can be user defined or can be based on specified use cases provided by the profile. The CDA document summary sections can be rendered for viewing. Content in some CDA document summary sections can be imported when possible (i.e.contains discrete entries) by the consuming system if desired.  
 +
*A received CDA document can be rendered showing sections summarizing information defined by the user. Note the receiver does not alter the received CDA document.
 +
*A received CDA document can be rendered showing sections summarizing information defined by use cases provided by the CDA-DSS profile. Note the receiver does not alter the received CDA document.
 
*A CDA document can be created to include sections summarizing information defined by the user.  
 
*A CDA document can be created to include sections summarizing information defined by the user.  
*A received CDA document can be rendered showing sections summarizing information defined by the user. Note the receiver does not alter the CDA document.
+
*A CDA document can be created to include sections summarizing information defined by summary section templates provided by the CDA-DSS profile.
*A CDA document can be created to include sections summarizing information defined by use cases defined by the CDA-DSS profile.
 
*A received CDA document can be rendered showing sections summarizing information defined by the CDA-DSS profile. Note the receiver does not alter the CDA document.
 
  
[[Image:CDA_DSSmarketingSlide.jpg|250px]]
+
 
 +
[[Image:CDA_DSSmarketingSlide.jpg|350px]]
  
 
==Benefits==
 
==Benefits==
CDA document can be very large and lengthy diminishing the need to provide the right amount of information needed to provide patient care. The CDA-DSS profile enables the ability to provide relevant and pertinent information in a CDA document by leveraging concise summary information. The information is provided in document summary sections supporting specific purposes that the document receiver and sender specifies. This allows large amounts of information in a CDA document to be provided along with summaries of pertinent information. This will assist with NOT overwhelming the person viewing the rendered document.
+
CDA documents can be very large and lengthy, diminishing the need to provide the right amount of information needed to provide efficient patient care. The CDA-DSS profile enables the ability to provide relevant and pertinent information in a CDA document by leveraging concise summary information. The information is provided in document summary sections supporting specific purposes that the document receiver and sender specifies. This allows large amounts of information in a CDA document to be provided along with summarization of pertinent information. This will assist by NOT overwhelming the person viewing the rendered document.
  
 
==Details==
 
==Details==
 +
The CDA-DSS profile enables the ability to provide relevant and pertinent information in CDA document sections that are concise, supporting specific purposes that the CDA docuement creator and receiver specifies. This allows the large amount of information in a CDA document to be provided yet at the same time not become overwhelming for the person viewing the rendered document.
  
''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+
A CDA document summary section can be constructed dynamically from existing data in the document and rendered for the user to view.
  
''<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.>''
+
A CDA document summary section, based on predefined section templates, can be constructed dynamically from existing data in the document and rendered for the user to view.
 +
 
 +
A CDA document summary section, based on predefined section templates, can be created by the document author
  
''<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==
  
Line 30: Line 32:
 
* HIE
 
* HIE
  
'''Actors & Transactions:'''
+
==Actors & Transactions==
  
 
* [[Content Creator]]
 
* [[Content Creator]]
Line 39: Line 41:
 
==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:'''  
 
+
[http://ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_TF_Vol2.pdf Volume 2 (PCC TF-2): Transactions and Content Modules]
''<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.>''
+
:* [http://ihe.net/uploadedFiles/Documents/PCC/IHE_PCC_Suppl_CDA_DSS_Rev2-1_TI_2019-09-27.pdf CDA-DSS Profile]
 
 
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
 
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
 
''<list all the standards on which the profile is based; if possible with links to sources>''
 
:* [http://dicom.nema.org DICOM]
 
 
:* [http://www.hl7.org HL7]
 
:* [http://www.hl7.org HL7]
:* ...
 
  
 
==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.>''
+
The [[Frameworks#IHE Patient Care Coordination Framework| Patient Care Coordination Framework]] is the official master document for this Profile.  
  
  
 
'''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.>''
+
None
 
 
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
 
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
 
* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
 
* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
 
* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
 
 
 
  
 
'''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>''
+
None
 
 
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>''
+
None
 
 
'''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. >''
 
  
[[Category:Profiles]]
+
[[Category:CDA]][[Category:Profiles]][[Category:Patient Care Coordination]]
  
This page is based on the [[Profile Overview Template]]
 
  
[[Category:Templates]]
 
<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
 
  
 
<!--  
 
<!--  

Latest revision as of 16:53, 15 April 2020

The CDA Document Summary Sections (CDA-DSS) Profile provides various types of CDA section templates that can summarize content in the CDA document or add summary content to a CDA document that is not already included in the document.

Summary

The CDA document summary sections can be created by summarizing pertinent information. The data that goes in the summary sections can be user defined or can be based on specified use cases provided by the profile. The CDA document summary sections can be rendered for viewing. Content in some CDA document summary sections can be imported when possible (i.e.contains discrete entries) by the consuming system if desired.

  • A received CDA document can be rendered showing sections summarizing information defined by the user. Note the receiver does not alter the received CDA document.
  • A received CDA document can be rendered showing sections summarizing information defined by use cases provided by the CDA-DSS profile. Note the receiver does not alter the received CDA document.
  • A CDA document can be created to include sections summarizing information defined by the user.
  • A CDA document can be created to include sections summarizing information defined by summary section templates provided by the CDA-DSS profile.


CDA DSSmarketingSlide.jpg

Benefits

CDA documents can be very large and lengthy, diminishing the need to provide the right amount of information needed to provide efficient patient care. The CDA-DSS profile enables the ability to provide relevant and pertinent information in a CDA document by leveraging concise summary information. The information is provided in document summary sections supporting specific purposes that the document receiver and sender specifies. This allows large amounts of information in a CDA document to be provided along with summarization of pertinent information. This will assist by NOT overwhelming the person viewing the rendered document.

Details

The CDA-DSS profile enables the ability to provide relevant and pertinent information in CDA document sections that are concise, supporting specific purposes that the CDA docuement creator and receiver specifies. This allows the large amount of information in a CDA document to be provided yet at the same time not become overwhelming for the person viewing the rendered document.

A CDA document summary section can be constructed dynamically from existing data in the document and rendered for the user to view.

A CDA document summary section, based on predefined section templates, can be constructed dynamically from existing data in the document and rendered for the user to view.

A CDA document summary section, based on predefined section templates, can be created by the document author

Systems Affected

  • EHR Systems used in healthcare delivery.
  • PHR
  • Patient Portal
  • HIE

Actors & Transactions

CDA-DSS ActorTransactionDiagram.jpg

Specification

Profile Status: Trial Implementation

Documents: Volume 2 (PCC TF-2): Transactions and Content Modules

Underlying Standards:

See Also

The Patient Care Coordination Framework is the official master document for this Profile.


Related Profiles

None

Consumer Information

None

Implementer Information

None