Difference between revisions of "XDS-SD OID"

From IHE Wiki
Jump to navigation Jump to search
(New page: Back to: XDS-SD_Harmonization __TOC__ <!-- <noinclude> {{:PCC TF-1/Header|Scanned Documents (XDS-SD)}} </noinclude> --> ==Scanned Documents Content Integration Profile== A variety of ...)
Line 1: Line 1:
Back to: [[XDS-SD_Harmonization]]
Back to: [[XDS-SD_Harmonization]]
<!-- <noinclude>
{{:PCC TF-1/Header|Scanned Documents (XDS-SD)}}
==Scanned Documents Content Integration Profile==
A variety of legacy paper, film, electronic and scanner outputted formats are used to store and exchange clinical documents. These formats are not designed for healthcare documentation, and furthermore, do not have a uniform mechanism to store healthcare metadata associated with the documents, including patient identifiers, demographics, encounter, order or service information.  The association of structured, healthcare metadata with this kind of document is important to maintain the integrity of the patient health record as managed by the source system. It is necessary to provide a mechanism that allows such source metadata to be stored with the document.
This profile defines how to couple such information, represented within a structured HL7 CDA R2 header, with a PDF or plaintext formatted document containing clinical information. Furthermore, this profile defines elements of the CDA R2 header necessary to minimally annotate these documents. Such header elements include information regarding patient identity, patient demographics, scanner operator identity, scanning technology, scan time as well as best available authoring information.  Portions of CDA R2 header, along with supplemental document registration information, are then used to populate XDS Document Entry metadata.
The content of this profile is intended for use in XDS, XDR and XDM. Content is created by a Content Creator and is to be consumed by a Content Consumer.  The Content Creator can be embodied by a Document Source Actor or a Portable Media Creator, and the Content Consumer by a Document Consumer, a Document Recipient or a Portable Media Importer. Obligations imposed on the Content Creator and the Content Consumer by this profile are understood to be fulfilled by the software that creates the final document for submission and/or consumes profile conformant documents rather than any particular scanning technology.
<pre>Add the following row(s) to the list of dependencies</pre>
{|style='background-color:#7f7f7f;' align='center' border='1' cellspacing='0'
!Integration Profile
!Dependency Type
|- style='background-color:#ffffff;' align='center'
|XDS-SD is a conformant HL7 CDA R2 document
|XDS-Lab constrains CDA R2 for the purposes of communicating scanned content
|- style='background-color:#ffffff;' align='center'
|PDF RFC 3778, The application/pdf Media Type (informative)
|- style='background-color:#ffffff;' align='center'
|PDF/A ISO 19005-1. Document management - Electronic document file format for long-term preservation - Part 1: Use of PDF (PDF/A)
{{Content Profile Actors and Transactions|PHLab}}
{{PCC Content Profile Options|PHLab|Creator=}}
{{:PCC TF-1/Coded Terminologies}}
{{XD* Binding|Scanned Documents|XDS-SD|
Bindings={{Binding|Scanned Documents}}
===XDS Scanned Document Content Module===
====Content Use Cases====
'''Text Chart Notes'''
Examples of this content include handwritten, typed or word processed clinical documents and/or chart notes.
These documents are typically multi-page, narrative text.  They include preprinted forms with handwritten responses, printed documents, and typed and/or word processed documents, and documents saved in various word processing formats. Appropriate formats are PDF, derived from the word processing format, or plaintext, if the text structure is all that needs to be conveyed. PDF is desirable because it most faithfully renders word processed document content.
'''Graphs, Charts and/or Line Drawings'''
Examples of this content include Growth Charts, Fetal Monitoring Graphs.
Line drawings such as those described above are best rendered using PDF versus an image based compression, such as JPEG.  However, when computer generated PDFs include lines, PDF vector encoding should be used.
'''Object Character Recognition (OCR) Scanned Documents'''
Clinical documents can contain text and annotations that cannot be fully processed by optical character recognition (OCR).  We call attention to the fact that the OCR text content may only partially represent the document content. These are best supported by converting to PDF format, which can mix the use of OCR’d text, compressed scanned text, and scanned image areas.
'''Electronic Documents'''
Existing clinical documents that are electronically transmitted or software created (e.g. PDF, or plaintext) can be considered as actually scanned, previously scanned or virtually scanned before they are shared.  In this context, “actually scanned” refers to electronic documents, newly created via some scanning technology from legacy paper or film for the purposes of sharing. “Previously scanned” refers to electronic documents that were previously produced via some scanning technology from legacy paper or film, but have existed in their own right for a period of time. “Virtually Scanned” electronic documents are existing electronic documents not derived from legacy paper or film that either are PDF/A or plaintext format or have been converted to one of these formats for the purposes of sharing. This content is covered by this profile.
====Content Creator Use Cases====
Content is created by a Content Creator. Impact on application function and workflow is implementation specific and out of scope of this content profile, though we note that they will be compliant with this content profile if they can produce CDA wrapped PDF, CDA wrapped plaintext or both. The following example use case is included to aid in the scoping of this content profile.
Legacy Clinic is a small two-physician clinic.  They presently store their patient's medical records on paper.  The Clinic is trying to figure out what to do with its paper and word processing documents as it converts over to an electronic system.  They plan would like to be able to view the files over their local intranet.
Presently, most records are handwritten on preprinted paper forms that are inserted into specific sections of the patient's chart.  More detailed encounter reports are dictated and sent to a transcription company that returns them in a word processing format. The medical records clerk at Legacy Clinic receives these files via e-mail, decrypts them, prints them out, and adds them to the patient's chart in the correct section.
Over the years, Legacy Clinic has used a number of different transcription companies, and the documents are stored in a variety of word processing formats.  Several years ago, they began to require that returned documents be in RTF format in an attempt to reduce frustrations induced by dealing with discrepant word processing formats.  Only in some cases was patient and encounter metadata stored within the word processing document in a regular format, depending upon the transcription company used at the time.
A third party presently handles labs for the clinic.  These are usually returned to the Clinic as printed documents.  The clerk inserts these into the labs section in the patient's chart.
In the case of Legacy Clinic, the link between the word processing documents and the patient has been maintained for many of its documents, since the existing manual process maintains that association, and some of the files also contain the encounter metadata.  However, the link to the specific encounter will need to be reestablished by interpreting the document content, which will require a great deal of manual effort for some of their documents which do not have it, and will still require custom handling depending upon the format used to store this metadata.
Legacy Clinic uses a transcription provider that can generate PDF documents, wrapped in a CDA Release 2.0 header.  These are sent to Legacy Clinic via e-mail.  While the same manual process is used, these documents are now in a format that is ready to be used by their new EHR system.
====Content Consumer Use Cases====
Content is consumed by a Content Consumer. Impact on application function and workflow is implementation specific and out of scope of this content profile. However, we note that adoption of this profile will necessitate the Content Consumer, upon document receipt, support the processing of both CDA wrapped PDF and CDA wrapped plaintext.
====Content Creation Process====
This profile assumes the following sequence of events in creation of an XDS-SD document.
#A legacy paper document is scanned and a PDF/A is rendered. Alternatively, an electronic document is converted, if necessary, to PDF/A or plaintext format (see ?7.1.3 and ?7.1.4).
#Software, conformant to this profile and most likely with the aid of user input (ex. to provide document title, confidentiality code, original author), renders the CDA R2 header pertaining to the PDF or plaintext produced. The document is wrapped and the XDS-SD document is completed (see ?7.1.8).
#XDS metadata is produced from data contained in the CDA header and supplemental information (see ?7.1.5).
#The completed XDS-SD document and corresponding metadata is sent via the Provide an Register Document Set Transaction [ITI-15] of XDS/XDR, or the Distribute Document Set on Media Transaction [ITI-32] of XDM.
===Grouping with Other Actors===
====Cross Enterprise Document Sharing, Media Interchange and Reliable Messaging====
The Content Creator and Content Consumer Actors shall be grouped with appropriate actors from the XDS, XDM or XDR integration profiles to support sharing of PHLab documents.
====Document Digital Signature (DSG)====
Content Creator actors should digitally sign all documents using the Digital Signature (DSG) Content Profile.
Content Consumer actors should verify the Digital Signature of the submission set before use of the information it contains.
Line 110: Line 21:
<!-- {{Std|CCD}} -->
|Parent=|ParentName=Medical Summary <--! parent is CDA, not medical summary -->
|Parent=|ParentName=Medical Summary <--! parent is CDA, not medical summary -->
|Index={{T|Data Elements|HL7 Care Record Summary|CDA Release 2.0|
|Index={{T|Data Elements|HL7 Care Record Summary|CDA Release 2.0|
Line 135: Line 44:
=====ClinicalDocument Header Content Modules====
====ClinicalDocument Header Content Modules====
The table [[#Specification|above]] lists the additional requirements (conformance statements) for this laboratory report which are in the form of header content modules.
The table [[#Specification|above]] lists the additional requirements (conformance statements) for this laboratory report which are in the form of header content modules.
====ClinicalDocument Header Example====
====ClinicalDocument Header Example====

Revision as of 16:41, 19 May 2008

Back to: XDS-SD_Harmonization

Development Only

The PCC Wiki Content is used only for development of IHE PCC Content. The Normative content of the PCC Technical Framework and the current supplements can be found at http://www.ihe.net/Technical_Framework/index.cfm#PCC

Trial.gif Scanned Document Specification tbd

This section outlines the content of the HL7 CDA R2 wrapper for the document. We note here that requirements specified below are to ensure the presence of a minimum amount of wrapper data in order to enhance description and facilitate sharing of the document. Implementers of this profile can and should make use of additional annotation within the CDA header to provide richer context. The examples in the following sections contain the minimal amount of wrapper data, as specified, and in many cases do make use of additional CDA header elements for enriched context. Assumptions and Definitions We assume that the scanning facility and equipment within it are assigned an OID and that the scanning facility assembles the wrapped scanned content. More information regarding the construction of OIDS can be found in the ITI Technical Framework, Volume 2, Appendix B. We define the following nomenclature for entity roles concerned in forming the wrapper content.

  • Original content – Legacy paper or electronic document intended for wrapping.
  • Scanned content – Scanned or appropriately converted/encoded electronic version of the original content.
  • Original author – Author of the original content.
  • (Scanner) Operator – Person assembling the scanned content.

Format Code

The XDSDocumentEntry format code for this content is urn:ihe:iti:xds-sd:2008

Parent Template

This document is an instance of the Medical Summary <--! parent is CDA, not medical summary --> template.

CDAR2 HL7 CDA Release 2.0
Data Element Index
Data Elements HL7 Care Record Summary CDA Release 2.0
Original Author ? author
Scanner ? author
Scanner Operator ? dataEnterer
Data Element Name Opt Template ID
Original Author C tbd
Scanner C tbd
Scanner Operator C tbd


CDA Release 2.0 documents that conform to the requirements of this content module shall indicate their conformance by the inclusion of the appropriate <templateId> elements in the header of the document. This is shown in the sample document below. A CDA Document may conform to more than one template. This content module inherits from the Medical Summary <--! parent is CDA, not medical summary --> content module, and so must conform to the requirements of that template as well, thus all <templateId> elements shown in the example below shall be included.

Sample Scanned Document Document
<ClinicalDocument xmlns='urn:hl7-org:v3'>
  <typeId extension="POCD_HD000040" root="2.16.840.1.113883.1.3"/>
  <templateId root=''/>
 <templateId root='tbd'/> <id root=' ' extension=' '/> <code code=' ' displayName=' ' codeSystem='2.16.840.1.113883.6.1' codeSystemName='LOINC'/> <title>Scanned Document</title> <effectiveTime value='20220706012005'/> <confidentialityCode code='N' displayName='Normal' codeSystem='2.16.840.1.113883.5.25' codeSystemName='Confidentiality' /> <languageCode code='en-US'/> : <component><structuredBody>     </structuredBody></component> </ClinicalDocument>
<pattern name='Template_tbd'>
 <rule context='*[cda:templateId/@root="tbd"]'>
   <!-- Verify that the template id is used on the appropriate type of object -->
   <assert test='../cda:ClinicalDocument'>
     Error: The Scanned Document can only be used on Clinical Documents.
   <!-- Verify that the parent templateId is also present. -->
   <assert test='cda:templateId[@root=""]'>
     Error: The parent template identifier for Scanned Document is not present.
   <!-- Verify the document type code -->
   <assert test='cda:code[@code = "{{{LOINC}}}"]'>
     Error: The document type code of a Scanned Document must be {{{LOINC}}}
   <assert test='cda:code[@codeSystem = "2.16.840.1.113883.6.1"]'>
     Error: The document type code must come from the LOINC code 
     system (2.16.840.1.113883.6.1).
   <assert test='.//cda:templateId[@root = "tbd"]'>
     See http://wiki.ihe.net/index.php?title=tbd
   <assert test='.//cda:templateId[@root = "tbd"]'>
     See http://wiki.ihe.net/index.php?title=tbd
   <assert test='.//cda:templateId[@root = "tbd"]'>
     See http://wiki.ihe.net/index.php?title=tbd

ClinicalDocument Header rendering


ClinicalDocument Header constraints

<template id=""/>

ClinicalDocument/templateId shall be present and shall have root value of "tbd" to signify that this ClinicalDocument conforms to the XDS-Lab content profile specification.


ClinicalDocument Header Content Modules

The table above lists the additional requirements (conformance statements) for this laboratory report which are in the form of header content modules.

ClinicalDocument Header Example

ClinicalDocument Body

The scanned document shall have a nonXMLBody.

ClinicalDocument Body Example