deutsche Nachrichtenprofile: XDS-MDM-CDA-Mapping

Aus Hl7wiki
Nachrichtenprofile
Wechseln zu: Navigation, Suche
Under construction icon-blue.svg
 This article or section is in the middle of an expansion or major restructuring and is not yet ready for use. You are welcome to assist in its construction by editing it as well. If this article has not been edited in several days, please remove this template.
This article was last edited by Foemig (talk| contribs) 10 years ago. (Purge)
Diese Seite oder Abschnitt ist derzeit ein Entwurf und ist noch nicht fertiggestellt. Du bist eingeladen, bei der Fertigstellung mitzuwirken. Wenn dieser Beitrag länger als einige Tage nicht editiert wurde, entferne diese Vorlage.
This article was last edited by Foemig (talk| contribs) 10 years ago. (Purge)
Logo-hl720.jpg
{{{Title}}}
deutsche Nachrichtenprofile: XDS-MDM-CDA-Mapping
Nachrichtenprofile
vorgelegt von:
HL7-Deutschland
ballotiert
Version: 01
Datum: 20. Dezember 2013
Status: Si-draft.svg Entwurf
Verfahren: {{{Verfahren}}}
Realm: Flag de.svg Deutschland
Copyright © 2013: HL7 Deutschland


Abstimmungsdokument 
Version Datum Status Realm
01 15.08.2013 ballotiert Flag de.svg Deutschland
Document PDF.svg noch kein download verfügbar
Kontributoren 
Logo-Agfa.jpg Agfa HealthCare GmbH Bonn
Logo icw.jpg InterComponentWare Walldorf
Logo ebpg.jpg eBPG NRW


Mapping XDS - CDA - MDM

Erläuterungen zu den Spalten:

  • Entry Type:
    • D=Document,
    • S=Submission set
    • F=Folder
  • XDS.b Attribute:
  • DataType:
  • Optionality
    • R = Required,
    • R2= Required if Known, O
    • = Optional,
    • P= Registry not required to support this in a query,
    • Cp = Computed/Assigned by Repository, required in register transaction.,
    • Cg = Computed/Assigned by Registry,
    • Cx= Optionally Computed/Assigned by a Document Registry. See ITI-TF, Rev. 6, Vol. 3, Table 4.1-4.
  • Example: example of the request payload (ebXML)
  • Description
  • Data Item Origin:
    • <in/out>.<path> (<usage>), e. g. „in.TXA-9 (RE)" means that the data item originates from the field „TXA-9" of the input, having usage „RE" (required but may be empty)
  • CDA

Die Tabelle ist gemäß XDS-Attribut sortiert:

Entry Type XDS.b Attribute DT Optio- nality Example Description Data Item Origin CDA
D, S Author \* R2/R2 
<rim:Classification
classificationScheme="urn:uuid:93606bcf-9494-43ec-9b4e-a7748d1a838d"
classifiedObject="theDocument"
nodeRepresentation="">
<!-- nodeRepresentation intentionally left blank -->
<rim:Slot name="authorPerson">
<!-- shall be single valued -->
<rim:ValueList>
<rim:Value>name of author</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:Slot name="authorInstitution">
<!-- may be multivalued -->
<rim:ValueList>
<rim:Value> Some Hospital^^^^^^^^^1.2.3.4.5.6.7.8.9.1789.45</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:Slot name="authorRole">
<!-- may be multivalued -->
<rim:ValueList>
<rim:Value>name of role</rim:Value>
</rim:ValueList>
</rim:Slot>
<rim:Slot name="authorSpecialty">
<!-- may be multivalued -->
<rim:ValueList>
<rim:Value>specialty of author</rim:Value>
</rim:ValueList>
</rim:Slot>
</rim:Classification>
in.TXA-9 (R),

see also below

D, S authorInstitution XON R2/R <see above> XON-1,
XON.10		 in.TXA-9.14.1 (RE),

in.TXA-9.14.2 (RE),
in.TXA-9.14.3 (RE);
see parameter
mdm.originator.assigningFacility.firstComponentAsAssigningAuthority

ClinicalDocument/legalAuthenticator/assignedEntity/representedOrganization (O)
D, S authorPerson XCN R2/R <see above> XCN.1,
XCN.2 ,
XCN.3 ,
XCN.4 ,
XCN.5,
XCN.6,
XCN.9.2
XCN.9.3		 in.TXA-9.1 (RE),

in.TXA-9.2 (RE),
in.TXA-9.3 (RE),
in.TXA-9.4 (RE),
in.TXA-9.5 (RE),
in.TXA-9.6 (RE),
in.TXA-9.9.2(RE),
in.TXA-9.9.3 (RE)

ClinicalDocument/author/assignedAuthor (R)
D,S authorRole - R2/O <see above> Parameter

xdsb.authorRole.default

ClinicalDocument/author/functionCode (O)

ClinicalDocument/author/participationFunction (R)

D, S authorSpecialty - R2/O <see above> Parameter

xdsb.authorSpecialty.default

ClinicalDocument/author/assignedAuthor/Code (O)
D availabilityStatus - Cg/R Deprecated

Approved||||in.TXA.19 w/ mapping
„availabilityStatus-availabilityStatus";
see also Table HL70273

S, F availabilityStatus - Cg/R Submitted

Approved

<automatically assigned>
D classCode - R/R 
<rim:Classification
classificationScheme= "urn:uuid:41a5887f-8865-4c09-adf7-e362475b143a"
classifiedObject="theDocument"
nodeRepresentation="classCode" >
<rim:Name>
<rim:LocalizedString value="classCodeDisplayName"/>
</rim:Name>
<rim:Slot name="codingScheme">
<rim:ValueList>
<rim:Value>XDS Affinity Domain Specific Value</rim:Value> </rim:ValueList>
</rim:Slot>
</rim:Classification>
Domain specific
Vocab. Mapping 		in.TXA-2 (R) w/ mapping

„documentType-classCode";
see also Table HL70270

D classCode DisplayName - R/P <see above> Domain specific out.classCode w/ mapping

„classCode-classCodeDisplayName"

ClinicalDocument/code (R)
F codeList R/R 
<rim:Classification classificationScheme= "urn:uuid:1ba97051-7806-41a8-a48b-8fce7af683c5"
 classifiedObject="Folder" nodeRepresentation="codeList" > 
<rim:Name>
 <rim:LocalizedString value="codeListCodeDisplayName" />
 </rim:Name> <rim:Slot name="codingScheme"> 
<rim:ValueList>
 <rim:Value>XDS Affinity Domain Specific Value</rim:Value>
 </rim:ValueList>
 </rim:Slot> 
</rim:Classification>
Multi valued

Domain specific; list of codes specifying the type of clinical activity that resulted in placing these XDS Documents in this XDSFolder. These values are to be drawn for a vocabulary or coding scheme defined by the Clinical XDS Affinity Domain. When a new submission request associates XDS Documents (new submission or previously submitted) to an XDS Folder, the Code included in the codeList is appended to the existing list of codes for this Folder (if any) unless this code is already present in the list managed by the Registry for the same XDS-Folder

in.PV1-2 w/ mapping „patientClass-CodeList";

see also Table HL70004

F codeList DisplayName R/P <see above> out.codeList w/ mapping

„codeList-codeListDisplayName"

D, F comments - O/P 
<rim:Description>
<rim:LocalizedString value = "comments"/>
</rim:Description>
Domain specific N/A
S comments - O/P 
<rim:Description>
<rim:LocalizedString value = "comments"/>
</rim:Description>
Domain specific N/A
D confidentialityCode - R/P 
<rim:Classification
classificationScheme= "urn:uuid:f4f85eac-e6cb-4883-b524-f2705394840f"
classifiedObject="theDocument"
nodeRepresentation="confidentialityCode">
<rim:Name>
<rim:LocalizedString value="displayName"/>
</rim:Name>
<rim:Slot name="codingScheme">
<rim:ValueList>
<rim:Value>XDS Affinity Domain Specific Value</rim:Value> </rim:ValueList>
</rim:Slot>
</rim:Classification>
Domain specific in.TXA-18.1 (R) w/ mapping
„documentConfidentialityStatus-confidentialityCode";
see also Table HL70272 		ClinicalDocument/confidentialityCode (R)
S contentTypeCode R/R 
<rim:Classification classificationScheme= "urn:uuid:aa543740-bdda-424e-8c96-df4873be8500" 
classifiedObject="submissionSet" nodeRepresentation="contentTypeCode" > 
<rim:Name> 
<rim:LocalizedString value="contentTypeCodeDisplayName" /> 
</rim:Name> 
<rim:Slot name="codingScheme"> 
<rim:ValueList> 
<rim:Value>XDS Affinity Domain Specific Value
</rim:Value> 
</rim:ValueList> 
</rim:Slot> 
</rim:Classification>
Domain specific; code specifying the type of clinical activity that resulted in placing these XDS Documents in this XDS-Submission Set in.EVN-4 w/ mapping

„eventReasonCode-contentTypeCode"; See also Table HL70062.

S contentTypeCode DisplayName R/P <see above> Domain specific; out.contentTypeCode w/ mapping „contentTypeCode- contentTypeCodeDisplayName"
creationTime ClinicalDocument/effectiveTime (R)
D, F entryUUID UUID Cg/P 
<rim:ExtrinsicObject mimeType="application/pdf"
id="urn:uuid:a6e06ca8-0c75-4064-9e5c-88b9045a96f6"
objectType= "urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1"
> ...
<automatically assigned>
S entryUUID UUID Cg/O <rim:ExtrinsicObject mimeType="application/pdf"

id="urn:uuid:a6e06ca8-0c75-4064-9e5c-88b9045a96f6" objectType= "urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1" > ...

<automatically assigned>
D eventCodeList - O/R 
<rim:Classification
classificationScheme= "urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4"
classifiedObject="theDocument"
nodeRepresentation="eventCode" >
<rim:Name>
<rim:LocalizedString value="eventCodeDisplayName"/>
</rim:Name>
<rim:Slot name="codingScheme">
<rim:ValueList>
<rim:Value>XDS Affinity Domain Specific Value</rim:Value> </rim:ValueList>
</rim:Slot>
</rim:Classification>
Domain specific;
represents the main clinical acts, such as a colonoscopy or an appendectomy, being documented. In some cases, the event is inherent in the typeCode, such as a "History and Physical Report" in which the procedure being documented is necessarily a "History and Physical" act.

An event can further specialize the act inherent in the typeCode, such as where it is simply "Procedure Report" and the procedure was a "colonoscopy". If one or more eventCodes are included, they shall not conflict with the values inherent in the classCode, practiceSettingCode or typeCode, as such a conflict would create an ambiguous situation.

in.TXA-2 (R) w/ mapping „documentType-eventCodeList";

see also Table HL70270

ClinicalDocument/documentationOf/serviceEvent (O)
D eventCodeList DisplayName O/P <see above> Domain specific out.eventCodeListw/ mapping „eventCodeList-eventCodeListDisplayName"
D formatCode R/R 
<rim:Classification
classificationScheme= "urn:uuid:a09d5840-386c-46f2-b5ad-9c3699a4309d"
classifiedObject="theDocument"
nodeRepresentation="formatCode" >
<rim:Name>
<rim:LocalizedString value="name"/>
</rim:Name>
<rim:Slot name="codingScheme">
<rim:ValueList>
<rim:Value>XDS Affinity Domain Specific Value</rim:Value> </rim:ValueList>
</rim:Slot>
</rim:Classification>
ITI or Domain specific (TXA-2 (R) + OBX-5-2 (R) + OBX-5-3 (R) ) w/ mapping

„documentType_typeOfDate_dataSubtype-formatCode"

D hash SHA1 Cp/P 
<rim:Slot name="hash">
<rim:ValueList>
<rim:Value> da39a3ee5e6b4b0d3255bfef95601890afd80709 </rim:Value>
</rim:ValueList>
</rim:Slot>
<automaticall assigned> -
D healthcareFacility TypeCode R/R 
<rim:Classification
classificationScheme= "urn:uuid:f33fb8ac-18af-42cc-ae0e-ed0b0bdb91e1"
classifiedObject="theDocument"
nodeRepresentation="healthcareFacilityTypeCode" >
<rim:Name>
<rim:LocalizedString value="healthcareFacilityTypeCodeDisplayName"/>
</rim:Name>
<rim:Slot name="codingScheme">
<rim:ValueList>
<rim:Value>XDS Affinity Domain Specific Value</rim:Value> </rim:ValueList>
</rim:Slot>
</rim:Classification>
Domain specific;

the type of organizational setting of the clinical encounter during which the documented act occurred

(EVN-7 transformed using mdm.eventFacility. firstComponentAsAssigningAuthority) w/ mapping „eventFacility-healthcareFacilityTypeCode"
D healthcareFacility TypeCode DisplayName R/P <see above> Domain specific out. healthcareFacility TypeCode w/ mapping „healthcareFacility TypeCode- healthcareFacility TypeCodeDisplayName"
D, S homeCommunityId 64 char OID as URI Cx/O <automatically assigned>
S intendedRecipient XON/ XCN O/O 
<rim:Slot name="intendedRecipient">
<rim:ValueList>
<rim:Value> Some Hospital^^^^^^^^^1.2.3.4.5.6.7.8.9.1789.45|^Wel^Marcus^^^Dr^MD</rim:Value>
<rim:Value> Some Hospital^^^^^^^^^1.2.3.4.5.6.7.8.9.1789.45|^Al^Peter^^^Dr^MD</rim:Value>
<rim:Value>|12345^John^Smith^^^Dr^MD</rim:Value>
<rim:Value>Main Hospital^^^^^^^^^1.2.3.4.5.6.7.8.9.
organization(s) or person(s) for whom the Submission set is intended <N/A>
D, S, F languageCode R/P 
<rim:Slot name="languageCode">
<rim:ValueList>
<rim:Value>en-us</rim:Value>
</rim:ValueList>
</rim:Slot>
parameter

xdsb.languageCode.default

ClinicalDocument/languageCode (R)
F lastUpdateTime DTM Cg/R 
<rim:Slot name="lastUpdateTime"> 
<rim:ValueList> 
<rim:Value>20041225212010</rim:Value> 
</rim:ValueList> 
</rim:Slot>
<automatically assigned>
D, S, F legalAuthenticator XCN O/O 
<rim:Slot name="legalAuthenticator">
<rim:ValueList>
<rim:Value>^Welby^Marcus^^^Dr^MD</rim:Value>
</rim:ValueList>
</rim:Slot>
XCN.1,

XCN.2 ,
XCN.3 ,
XCN.4 ,
XCN.5,
XCN.6,
XCN.9.2
XCN.9.3

in.TXA-22.1 (RE),

in.TXA-22.2 (CE),
in.TXA-22.3 (CE),
in.TXA-22.4 (CE),
in.TXA-22.5 (CE),
in.TXA-22.6 (CE),
in.TXA-22.9.2 (CE),
in.TXA-22.9.3 (CE)

ClinicalDocument/legalAuthenticator/assignedEntity (O)
L parentDocument ReationshipCode O/P urn:ihe:iti:2007:AssociationType:RPLC

urn:ihe:iti:2007:AssociationType:XFRM
urn:ihe:iti:2007:AssociationType:APND
urn:ihe:iti:2007:AssociationType:XFRM_RPLC

input.MSH-9-2,

hardcoded mapping
T06 -> APND
T08 -> RPLC

ClinicalDocument/relatedDocument/parentDocument/id (O)
D mimeType R/P 
<rim:ExtrinsicObject mimeType="application/pdf"
id="theDocument"
objectType= "urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1"
> ...
(OBX-5-2 (R) w/ mapping „typeOfData-mimeTypePrefix") +

(OBX-5-3 (R) in lower case and prepended with „/"); see also Table HL70191; see also Table HL70291

D, S, F patientId CX R/R PID-3 (R)
D practiceSetting Code R/R 
<rim:Classification
classificationScheme= "urn:uuid:cccf5598-8b07-4b77-a05e-ae952c785ead"
classifiedObject="theDocument"
nodeRepresentation="practiceSettingCode" >
<rim:Name>
<rim:LocalizedString value="practiceSettingCodeDisplayName" />
</rim:Name>
<rim:Slot name="codingScheme">
<rim:ValueList>
<rim:Value>XDS Affinity Domain Specific Value</rim:Value> </rim:ValueList>
</rim:Slot>
</rim:Classification>
Domain specific;

clinical specialty where the act that resulted in the document was performed (e.g. Familly Practice, Laboratory, Radiology). It is suggested that the XDS Affinity Domain draws these values from a coding scheme providing a coarse level of granularity (about 10 to 100 entries); single value.

(EVN-7 transformed using mdm.eventFacility. firstComponentAsAssigningAuthority) +

mapping „eventFacility-practiceSettingCode"

D practiceSetting CodeDisplayName R/P 
<rim:Classification
classificationScheme= "urn:uuid:cccf5598-8b07-4b77-a05e-ae952c785ead"
classifiedObject="theDocument"
nodeRepresentation="practiceSettingCode" >
<rim:Name>
<rim:LocalizedString value="practiceSettingCodeDisplayName" />
</rim:Name>
<rim:Slot name="codingScheme">
<rim:ValueList>
<rim:Value>XDS Affinity Domain Specific Value</rim:Value> </rim:ValueList>
</rim:Slot>
</rim:Classification>
Domain specific; out.practiceSetting w/ mapping „practiceSetting-practiceSettingDisplayName"
D repositoryUniqueId Cp/P 
<rim:Slot name="repositoryUniqueId">
<rim:ValueList>
<rim:Value>1.3.6.1.4…</rim:Value>
</rim:ValueList>
</rim:Slot>
<automatically assigned>
D serviceStartTime DTM R2/R 
<rim:Slot name="serviceStartTime">
<rim:ValueList>
<rim:Value>20041225212010</rim:Value>
</rim:ValueList>
</rim:Slot>
if (useEncounterDataForServiceTime) 
 in.PV1-44 (RE)

else 

 in.TXA-4 (R)
ClinicalDocument/documentationoOf/serviceEvent/effectiveTime/low/@value
D serviceStopTime DTM R2/R 
<rim:Slot name="serviceStopTime">
<rim:ValueList>
<rim:Value>20041225232010</rim:Value>
</rim:ValueList>
</rim:Slot>
if (useEncounterDataForServiceTime) 
 in. PV1-45 (RE)
else 
 <nothing>
ClinicalDocument/documentationoOf/serviceEvent/effictiveTime/high/@value
D, S, F size Integer Cp/P 
<rim:Slot name="size">
<rim:ValueList>
<rim:Value>3654</rim:Value>
</rim:ValueList>
</rim:Slot>
<automatically assigned>
S sourceId OID R/R 
<rim:ExternalIdentifier
identificationScheme= "urn:uuid:554ac39e-e3fe-47fe-b233-965d2a147832"
value="1.3.6.1.4.1.21367.2005.3.7" >
<rim:Name>
<rim:LocalizedString value = "XDSSubmissionSet.sourceId"/>
OID identifying the instance of the Document Source that contributed the Submission Set. When a "broker" is involved in sending submission sets from a collection of client systems, it should use a different source ID for submissions from each separate system to allow for tracking;

single value.

(in.EVN-7 transformed using mdm.eventFacility. firstComponentAsAssigningAuthority) w/ mapping „eventFacility-sourceId"
D sourcePatientId CX R/P 
<rim:Slot name="sourcePatientId">
<rim:ValueList>
<rim:Value>j98789^^^id.domain</rim:Value>
</rim:ValueList>
</rim:Slot>
in.PID-3 (R) ClinicalDocument/recordTarget/PatientRole/id (R)
D sourcePatientInfo O/P 
<rim:Slot name="sourcePatientInfo"> 
<rim:ValueList> 
<rim:Value>PID-3|DTP-1^^^&amp;1.3.6.1.4.1.21367.2005.3.7&amp;ISO</rim:Value> 
<rim:Value>PID-5|DICTAPHONE^ONE^^^</rim:Value> 
<rim:Value>PID-7|19650120</rim:Value> <rim:Value>PID-8|M</rim:Value>
<rim:Value>PID-11|100 Main St^^BURLINGTON^MA^01803^USA</rim:Value>
</rim:ValueList> 
</rim:Slot>
PID-3 should include the source patient identifier.

PID-5 should include the patient name. PID-8 should code the patient gender as M – Male F – Female O – Other U – Unknown. PID-7 should include the patient date of birth.
PID-11 should include the patient address.
PID-2, PID-4, PID-12 and PID-19 should not be used. ||in.PID-2 (X),
in.PID-3 (RE),
in.PID-4 (X),
in.PID-5 (RE),
in.PID-8 (RE),
in.PID-7 (RE),
in.PID-11 (RE),
in.PID-12 (X),
in.PID-19 (X)

ClinicalDocument/recordTarget/PatientRole (R)
S submissionTime DTM R/R 
<rim:Slot name="submissionTime">
<rim:ValueList>
<rim:Value>20041225212010</rim:Value>
</rim:ValueList>
</rim:Slot>
no explicit submission sets => identical with document creation time if xdsb.submissionTime.useSystemTime == true

then <use system time> else in.TXA-6;

ClinicalDocument/effectiveTime (R)
D, S title O/P 
<rim:ExtrinsicObject
id="theDocument"
objectType= "urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1"
mimeType="application/pdf" >
<rim:Name>
<rim:LocalizedString value="title"/>
</rim:Name>
…
</rim:ExtrinsicObject>
<N/A> ClinicalDocument/title (O)
D typeCode R/R 
<rim:Classification
classificationScheme= "urn:uuid:41a5887f-8865-4c09-adf7-e362475b143a"
classifiedObject="theDocument"
nodeRepresentation="typeCode" >
<rim:Name>
<rim:LocalizedString value="typeCodeDisplayName" />
</rim:Name>
<rim:Slot name="codingScheme">
<rim:ValueList>
<rim:Value>XDS Affinity Domain Specific Value</rim:Value> </rim:ValueList>
</rim:Slot> </rim:Classification>
Domain specific;

precise kind of document (e.g. Pulmonary History and Physical, Discharge Summary, Ultrasound Report); single value

in.TXA-2 (R) w/ mapping „documentType-typeCode";

see also Table HL70270

ClinicalDocument/code (R)
D typeCode DisplayName R/P <see above> Domain specific out.typeCode w/ mapping

„typeCode-typeCodeDisplayName"

D uniqueId OID R/R 
<rim:ExternalIdentifier
identificationScheme= "urn:uuid:2e82c1f6-a085-4c72-9da3-8640a32e42ab"
value="1.3.6.1.4.1.21367.2005.3.7^11379" >
<rim:Name>
<rim:LocalizedString value="XDSDocumentEntry.uniqueId"/>
</rim:Name> </rim:ExternalIdentifier>
if in.TXA-12-1 is a valid OID, then:

in.TXA-12-1 (R); else if in.TXA-12-4 equals „ISO" then: in.TXA-12-3 (R) + "^" + in.TXA-12-1 (R); else raise error

ClinicalDocument/id (R)
F uniqueId OID R/R 
<rim:ExternalIdentifier
identificationScheme=
„urn:uuid:75df8f67-9973-4fbe-a900-df66cefecc5a"
value="1.3.6.1.4.1.21367.2005.3.7.3670984664">
<rim:Name>
<rim:LocalizedString value = „XDSFolder.uniqueId"/>
</rim:Name>
</rim:ExternalIdentifier>
implement strategy "prefixed number to oid""
S uniqueId OID R/R implement strategy "prefixed number to oid""
D URI URI Cp/P 
<rim:Slot name="URI"> 
<rim:ValueList> 
<rim:Value>1\|http://www.ihe.net/IHERetrieveDocument? 
</rim:Value> 
<rim:Value>2\|requestType=DOCUMENT&documentUID=1.2.3 
</rim:Value> 
<rim:Value>3\|&preferredContentType=application%2fpdf 
</rim:Value> 
</rim:ValueList> 
</rim:Slot>
<N/A>
Abgerufen von „https://wiki.hl7.de/index.php?title=XDS-MDM-CDA-Mapping&oldid=17822“