TF-PCC-CP-0031

From IHE Wiki
Jump to: navigation, search

Return to: PCC_Change_Proposals
Return to: PCC_TF-2/Bindings
Return to: XDS-SD_Harmonization

Change Proposal TF-PCC-CP-0031

Official Change Proposal Template is a WORD document found at ftp://ftp.ihe.net/Document_templates/IHE_Change_Proposal-Template-V10.doc

The Change Proposal Template that you use is dependent on the committee.

Tracking Information

Domain 
Patient Care Coordination
Change Proposal Number 
TF-PCC-CP-0031
Status 
incoming
Last Updated 
18:16, 19 June 2008 (CDT)
Assigned 
Unassigned

Change Proposal Summary

Title 
Edits to XD* Metadata Bindings for XDS-SD
Submission Date
18:16, 19 June 2008 (CDT)
Profile Affected
PCC-TF vol 2
TF Version
2020
Volume and Section

Rationale

Update Bindings with the following extensions for XDS-SD

Content

XDS-SD is a CDA R2 document and thus conforms to the XDS Metadata requirements in the PCC-TF, volume 2, Section 5 unless otherwise specified below.

XDSDocumentEntry

XDS-SD leverages the XDS DocumentEntry Metadata requirements in the PCC-TF, volume 2, Section 5.1.1.1.1 and in PCC_TF-2/Bindings unless otherwise specified below

XDSDocumentEntry.formatCode

The XDSDocumentEntry.formatCode shall be urn:ihe:iti:xds-sd:pdf:2008 when the document is scanned pdf and urn:ihe:iti:xds-sd:text:2008 when the document is scanned text. The formatCode codeSystem shall be 1.3.6.1.4.1.19376.1.2.3.

XDSDocumentEntry.uniqueId

This value shall be the ClinicalDocument/id in the HL7 CDA R2 header. The root attribute is required, and the extension attribute is optional. In accordance with the XDS.a profile, total length is limited to 128 characters; for XDS.b the limit is 256 characters. Additionally see PCC-TF, volume 2, Section 5.1.1.1.1 or PCC_TF-2/Bindings for further content specification.

Relating instances of XDS-SD documents

In general, most instances of XDS-SD will not have parent documents. It is possible, however, in some specific use cases that instances of XDS-SD documents are related. For example, for a particular document it may be the case that both the PDF scanned content and somewhat equivalent plaintext need to be wrapped and submitted. Each document would correspond to separate XDSDocumentEntries linked via an XFRM Association that indicates one document is a transform of the other. These can be submitted in a single submission set, or in separate ones. Other specific examples may exist and this profile does not preclude the notion of a parent document for these cases.

XDSSubmissionSet

No additional constraints. Particular to this profile, a legitimate use of submission sets would be to maintain a logical grouping of multiple XDS-SD documents. We encourage such usage. For more information, see PCC-TF-2 Section 5.1.1.1.2 or PCC_TF-2/Bindings.

XDSFolder

No additional requirements. For more information, see PCC-TF-2 Section 5.1.1.1.3 or PCC_TF-2/Bindings.