Difference between revisions of "PCC TF-2/Bindings"
m |
|||
Line 49: | Line 49: | ||
{{:Medical Document Binding to XDS, XDM and XDR}} | {{:Medical Document Binding to XDS, XDM and XDR}} | ||
− | |||
− |
Revision as of 08:12, 23 August 2007
IHE Patient Care Coordination Bindings
This section describes how the payload used in a transaction of an IHE profile is related to and/or constrains the data elements sent or received in those transactions. This section is where any specific dependencies between the content and transaction are defined.
A content integration profile can define multiple bindings. Each binding should identify the transactions and content to which it applies.
The source for all required and optional attributes have been defined in in the bindings below. Three tables describe the three main XDS object types: XDSDocumentEntry, XDSSubmissionSet, and XDSFolder. XDSSubmissionSet and XDSDocumentEntry are required. Use of XDSFolder is optional.
The columns of the following tables are:
- <XXX> attribute – name of an XDS attribute, followed by any discussion of the binding detail.
- Optional? - Indicates the required status of the XDS attribute, and is one of R, R2, or O (optional). This column is filled with the values specified in the XDS Profile as a convenience.
- Source Type – Will contain one of the following values:
Source Type | Description |
SA | Source document Attribute – value is copied directly from source document. The Source/Value column identifies where in the source document this attribute comes from. Specify the location in XPath when possible. |
SAT | Source document Attribute with Transformation – value is copied from source document and transformed. The Source/Value column identifies where in the source document this attribute comes from. Specify the location in XPath when possible. Extended Discussion column must not be empty and the transform must be defined in the extended discussion |
FM | Fixed (constant) by Mapping - for all source documents. Source/Value column contains the value to be used in all documents. |
FAD | Fixed by Affinity Domain – value configured into Affinity Domain, all documents will use this value. |
CAD | Coded in Affinity Domain – a list of acceptable codes are to be configured into Affinity Domain. The value for this attribute shall be taken from this list. |
CADT | Coded in Affinity Domain with Transform - a list of acceptable codes are to be configured into Affinity Domain. The value for this attribute shall be taken from this list. |
n/a | Not Applicable – may be used with an optionality R2 or O attribute to indicate it is not to be used. |
DS | Document Source – value comes from the Document Source actor. Use Source/Value column or Extended Discussion to give details. |
O | Other – Extended Discussion must be 'yes' and details given in an Extended Discussion. |
- Source/Value – This column indicates the source or the value used.
The following tables are intended to be summaries of the mapping and transforms. The accompanying sections labeled 'Extended Discussion' are to contain the details as necessary.
Medical Document Binding to XDS, XDM and XDR
This binding defines a transformation that generates metadata for the XDSDocumentEntry element of appropriate transactions from the XDS, XDM and XDR profiles given a medical document and information from other sources. The medical document refers to the document being stored in a repository that will be referenced in the registry. The other sources of information include the configuration of the Document Source actor, the Affinity Domain, the site or facility, local agreements, other documents in the registry/repository, and this Content Profile.
In many cases, the CDA document is created for the purposes of sharing within an affinity domain. In these cases the context of the CDA and the context of the affinity domain are the same, in which case the following mappings shall apply.
In other cases, the CDA document may have been created for internal use, and are subsequentyly being shared. In these cases the context of the CDA document would not neccessarily coincide with that of the affinity domain, and the mappings below would not necessarily apply.
Please note the specifics given in the table below.
XDSDocumentEntry Metadata
XDSDocumentEntry Attribute | Optional? | Source Type | Source/ Value |
---|---|---|---|
availabilityStatus | R | DS | |
authorInstitution | R2 | SAT |
$inst <=
/ClinicalDocument/author |
authorPerson | R2 | SAT |
$person <= /ClinicalDocument/author
|
authorRole | R2 | SAT | This metadata element should be based on a mapping of the participation function defined in the CDA document to the set of author roles configured for the affinity domain. If the context of the CDA coincides with that of the affinity domain, then the following x-path may be appropriate: /ClincicalDocument/author/ participationFunction |
authorSpecialty | R2 | SAT | This metadata element should be based on a mapping of the code associated with the assignedAuthor to detailed defined classification system for healthcare providers such configured in the affinitity domain. Possible classifications include those found in SNOMED-CT, or the HIPAA Healthcare Provider Taxonomy. If the context of the CDA coincides with that of the affinity domain, then the following x-path may be appropriate: /ClinicalDocument/author/ assignedAuthor/code |
classCode | R | CADT | Derived from a mapping of /ClinicalDocument/code/@code to an Affinity Domain specified coded value to use and coding system. Affinity Domains are encouraged to use the appropriate value for Type of Service, based on the LOINC Type of Service (see Page 53 of the LOINC User's Manual). Must be consistent with /ClinicalDocument/code/@code |
classCodeDisplayName | R | CADT | DisplayName of the classCode derived. Derived from a mapping of /ClinicalDocument/code/@code to the appropriate Display Name based on the Type of Service. Must be Consitent with /ClinicalDocument/code/@code |
confidentialityCode | R | CADT | Derived from a mapping of /ClinicalDocument/confidentialityCode/@code to an Affinity Domain specified coded value and coding system. When using the BPPC profile, the confidentialyCode may also be obtained from the <authorization> element.
|
comments | O | DS | |
creationTime | R | SAT | /ClinicalDocument/effectiveTime
|
entryUUID | R | DS | |
eventCodeList | O | CADT | These values express a collection of keywords that may be relevant to the consumer of the documents in the registry. They may come from anywhere in the CDA document, according to its purpose. |
eventCodeDisplayNameList | R (if event Code is valued) |
CADT | These are the display names for the collection of keywords described above. |
formatCode | R | FM | The format code for each PCC Document content profile is provided within the document specifications. |
healthcareFacilityTypeCode | R | CAD | A fixed value assigned to the Document Source and configured form a set of Affinity Domain defined values. Must be concistent with /clinicalDocument/code |
healthcareFacility TypeCodeDisplay Name |
R | CAD | Must be concistent with /clinicalDocument/code |
intendedRecipient (for XDR, XDM) | O | SAT |
$person <=
/ClinicalDocument/intendedRecipient
"^^^^^&", |
languageCode | R | SA | /ClinicalDocument/languageCode |
legalAuthenticator | O | SAT | $person <= /ClinicalDocument/ legalAuthenticator
|
mimeType | R | FM | text/xml |
parentDocumentRelationship | R (when applicable) |
DS | Local document versions need not always be published, and so no exact mapping can be determined from the content of the CDA document. The parentDocumentRelationship may be determined in some configurations from the relatedDocument element present in the CDA dsocument. If the context of the CDA coincides with that of the affinity domain, then the following x-path may be appropriate: /ClinicalDocument/relatedDocument/@typeCode |
parentDocumentId | R (when parent Document Relationship is present) |
DS | Local document versions need not always be published, and so no exact mapping can be determined from the content of the CDA document. The parentDocumentId may be determined in some configurations from the relatedDocument element present in the CDA dsocument. If the context of the CDA coincides with that of the affinity domain, then the following x-path may be appropriate: $docID <= /ClinicalDocument/ relatedDocument/parentDocument/id
|
patientId | R | DS | The XDS Affinity Domain patient ID can be mapped from the patientRole/id element using transactions from the ITI PIX or PDQ profiles. See sourcePatientId below. If the context of the CDA coincides with that of the affinity domain, then the following x-path may be appropriate:
|
practiceSettingCode | R | CAD | This elements should be based on a coarse classification system for the class of specialty practice. Recommend the use of the classification system for Practice Setting, such as that described by the Subject Matter Domain in LOINC. |
practiceSettingCodeDisplayName | R | CAD | This element shall contain the display names associated with the codes described above. |
serviceStartTime | R2 | SAT | /ClinicalDocument/documentationOf/ serviceEvent/effectiveTime/low/ @value
|
serviceStopTime | R2 | SAT | /ClinicalDocument/documentationOf/ serviceEvent/effectiveTime/high/ @value
|
sourcePatientId | R | SAT | $patID <= /ClinicalDocument/recordTarget/ patientRole/id
|
sourcePatientInfo | R | SAT | /ClinicalDocument/recordTarget/ patientRole
|
title | O | SA | /ClinicalDocument/title |
typeCode | R | CADT | /ClinicalDocument/code/@code
|
typeCodeDisplay Name |
R | CADT | /ClinicalDocument/code/@displayName |
uniqueId | R | SAT | $docID <= /ClinicalDocument/id
|
XDSSubmissionSet Metadata
The submission set metadata is as defined for XDS, and is not necessarily affected by the content of the clinical document. Metadata values in an XDSSubmissionSet with names identical to those in the XDSDocumentEntry may be inherited from XDSDocumentEntry metadata, but this is left to affinity domain policy and/or application configuration.
Use of XDS Submission Set
This content format uses the XDS Submission Set to create a package of information to send from one provider to another. All documents referenced by the Medical Summary in this Package must be in the submission set.
Use of XDS Folders
No specific requirements identified.
Configuration
IHE Content Profiles using this binding require that Content Creators and Content Consumers be configurable with institution and other specific attributes or parameters. Implementers should be aware of these requirements to make such attributes easily configurable. There shall be a mechanism for the publishing and distribution of style sheets used to view clinical documents.