Difference between revisions of "Medical Document Binding to XDS, XDM and XDR/zh"
Line 13: | Line 13: | ||
|-bgcolor='#cfcfcf' align='center' | |-bgcolor='#cfcfcf' align='center' | ||
!width='40%'|XDSDocumentEntry Attribute | !width='40%'|XDSDocumentEntry Attribute | ||
− | !width='20%'| | + | !width='20%'|XDS文档条目属性中文名称 |
!width='5%'|可选程度 | !width='5%'|可选程度 | ||
!width='5%'|来源类型 | !width='5%'|来源类型 | ||
!width='30%'|来源/取值 | !width='30%'|来源/取值 | ||
+ | !width='10%'|来源/取值中文说明 | ||
+ | |||
+ | | | ||
|- | |- | ||
|availabilityStatus | |availabilityStatus | ||
Line 23: | Line 26: | ||
|align = "center"|DS | |align = "center"|DS | ||
| | | | ||
+ | | | ||
|- | |- | ||
|authorInstitution | |authorInstitution | ||
Line 35: | Line 39: | ||
<!-- THIS IS CP 316 in ITI -- has not passed, yet, "<nowiki>^^^^^</nowiki>&",<br/>$inst/id/@root, "&ISO", "<nowiki>^^^^</nowiki>", $inst/id/@extension<br/> --> | <!-- THIS IS CP 316 in ITI -- has not passed, yet, "<nowiki>^^^^^</nowiki>&",<br/>$inst/id/@root, "&ISO", "<nowiki>^^^^</nowiki>", $inst/id/@extension<br/> --> | ||
+ | | | ||
|- | |- | ||
|authorPerson | |authorPerson | ||
Line 45: | Line 50: | ||
The author can be formatted using the following XPath expression, where '''$person''' in the expression below represents the author.<br/>concat(<br/> $person/id/@extension,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/family,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/given<nowiki>[</nowiki>1<nowiki>]</nowiki>,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/given<nowiki>[</nowiki>2<nowiki>]</nowiki>,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/suffix,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/prefix,"<nowiki>^</nowiki>",<br/> "<nowiki>^^^</nowiki>&", $person/id/@root,"&ISO")<br/> | The author can be formatted using the following XPath expression, where '''$person''' in the expression below represents the author.<br/>concat(<br/> $person/id/@extension,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/family,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/given<nowiki>[</nowiki>1<nowiki>]</nowiki>,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/given<nowiki>[</nowiki>2<nowiki>]</nowiki>,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/suffix,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/prefix,"<nowiki>^</nowiki>",<br/> "<nowiki>^^^</nowiki>&", $person/id/@root,"&ISO")<br/> | ||
+ | | | ||
|- | |- | ||
|authorRole | |authorRole | ||
Line 52: | Line 58: | ||
|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: <br/>/ClincicalDocument/author/<br/>participationFunction | |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: <br/>/ClincicalDocument/author/<br/>participationFunction | ||
+ | | | ||
|- | |- | ||
|authorSpecialty | |authorSpecialty | ||
Line 59: | Line 66: | ||
|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: <br/>/ClinicalDocument/author/<br/>assignedAuthor/code | |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: <br/>/ClinicalDocument/author/<br/>assignedAuthor/code | ||
+ | | | ||
|- | |- | ||
|classCode | |classCode | ||
Line 65: | Line 73: | ||
|align = "center"|CADT | |align = "center"|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<nowiki>'</nowiki>s Manual). Must be consistent with /ClinicalDocument/code/@code | |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<nowiki>'</nowiki>s Manual). Must be consistent with /ClinicalDocument/code/@code | ||
+ | | | ||
|- | |- | ||
|classCodeDisplayName | |classCodeDisplayName | ||
Line 71: | Line 80: | ||
|align = "center"|CADT | |align = "center"|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 | |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 | |confidentialityCode | ||
Line 79: | Line 89: | ||
<br/> | <br/> | ||
/ClinicalDocument/<br/>confidentialityCode/@code<br/> -AND/OR-<br/>/ClinicalDocument/authorization/<br/>consent<nowiki>[</nowiki><br/> templateId/@root=<br/><nowiki>'</nowiki>1.3.6.1.4.1.19376.1.5.3.1.2.5<nowiki>'</nowiki><br/><nowiki>]</nowiki> /code/@code | /ClinicalDocument/<br/>confidentialityCode/@code<br/> -AND/OR-<br/>/ClinicalDocument/authorization/<br/>consent<nowiki>[</nowiki><br/> templateId/@root=<br/><nowiki>'</nowiki>1.3.6.1.4.1.19376.1.5.3.1.2.5<nowiki>'</nowiki><br/><nowiki>]</nowiki> /code/@code | ||
+ | | | ||
|- | |- | ||
|comments | |comments | ||
Line 85: | Line 96: | ||
|align = "center"|DS | |align = "center"|DS | ||
| | | | ||
+ | | | ||
|- | |- | ||
|creationTime | |creationTime | ||
Line 95: | Line 107: | ||
Times specified in clinical documents may be specified with a precision in fractional sections, and may contain a time zone offset. In the XDS Metadata, it can be precise to the second, and is always given in UTC, so the timezone offset if present must be added to the current time to obtain the UTC time. | Times specified in clinical documents may be specified with a precision in fractional sections, and may contain a time zone offset. In the XDS Metadata, it can be precise to the second, and is always given in UTC, so the timezone offset if present must be added to the current time to obtain the UTC time. | ||
+ | | | ||
|- | |- | ||
|entryUUID | |entryUUID | ||
Line 101: | Line 114: | ||
|align = "center"|DS | |align = "center"|DS | ||
| | | | ||
+ | | | ||
|- | |- | ||
|eventCodeList | |eventCodeList | ||
Line 107: | Line 121: | ||
|align = "center"|CADT | |align = "center"|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. | |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 | |eventCodeDisplayNameList | ||
Line 113: | Line 128: | ||
|align = "center"|CADT | |align = "center"|CADT | ||
|These are the display names for the collection of keywords described above. | |These are the display names for the collection of keywords described above. | ||
+ | | | ||
|- | |- | ||
|formatCode | |formatCode | ||
Line 119: | Line 135: | ||
|align = "center"|FM | |align = "center"|FM | ||
|The format code for each PCC Document content profile is provided within the document specifications. | |The format code for each PCC Document content profile is provided within the document specifications. | ||
+ | | | ||
|- | |- | ||
|healthcareFacilityTypeCode | |healthcareFacilityTypeCode | ||
Line 125: | Line 142: | ||
|align = "center"|CAD | |align = "center"|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 | |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<br/>TypeCodeDisplay<br/>Name | |healthcareFacility<br/>TypeCodeDisplay<br/>Name | ||
Line 131: | Line 149: | ||
|align = "center"|CAD | |align = "center"|CAD | ||
|Must be concistent with /clinicalDocument/code | |Must be concistent with /clinicalDocument/code | ||
+ | | | ||
|- | |- | ||
|intendedRecipient (for XDR, XDM) | |intendedRecipient (for XDR, XDM) | ||
Line 150: | Line 169: | ||
"<nowiki>^^^^^</nowiki>&",<br/>$inst/id/@root, "&ISO", "<nowiki>^^^^</nowiki>", $inst/id/@extension)<br/>--> | "<nowiki>^^^^^</nowiki>&",<br/>$inst/id/@root, "&ISO", "<nowiki>^^^^</nowiki>", $inst/id/@extension)<br/>--> | ||
+ | | | ||
|- | |- | ||
|languageCode | |languageCode | ||
Line 156: | Line 176: | ||
|align = "center"|SA | |align = "center"|SA | ||
|/ClinicalDocument/languageCode | |/ClinicalDocument/languageCode | ||
+ | | | ||
|- | |- | ||
|legalAuthenticator | |legalAuthenticator | ||
Line 165: | Line 186: | ||
The legalAuthenticator can be formatted using the following XPath expression, where '''$person''' in the expression below represents the legalAuthenticator.<br/>concat(<br/> $person/id/@extension,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/family,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/given<nowiki>[</nowiki>1<nowiki>]</nowiki>,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/given<nowiki>[</nowiki>2<nowiki>]</nowiki>,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/suffix,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/prefix,"<nowiki>^</nowiki>",<br/> "<nowiki>^^^</nowiki>&", $person/id/@root,"&ISO")<br/> | The legalAuthenticator can be formatted using the following XPath expression, where '''$person''' in the expression below represents the legalAuthenticator.<br/>concat(<br/> $person/id/@extension,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/family,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/given<nowiki>[</nowiki>1<nowiki>]</nowiki>,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/given<nowiki>[</nowiki>2<nowiki>]</nowiki>,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/suffix,"<nowiki>^</nowiki>",<br/> $person/assignedPerson/name/prefix,"<nowiki>^</nowiki>",<br/> "<nowiki>^^^</nowiki>&", $person/id/@root,"&ISO")<br/> | ||
+ | | | ||
|- | |- | ||
|mimeType | |mimeType | ||
Line 171: | Line 193: | ||
|align = "center"|FM | |align = "center"|FM | ||
|text/xml | |text/xml | ||
+ | | | ||
|- | |- | ||
|parentDocumentRelationship | |parentDocumentRelationship | ||
Line 177: | Line 200: | ||
|align = "center"|DS | |align = "center"|DS | ||
|Local document versions need not always be published, and so no exact mapping can be determined from the content of the CDA document.<br/>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: <br/>/ClinicalDocument/relatedDocument/@typeCode | |Local document versions need not always be published, and so no exact mapping can be determined from the content of the CDA document.<br/>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: <br/>/ClinicalDocument/relatedDocument/@typeCode | ||
+ | | | ||
|- | |- | ||
|parentDocumentId | |parentDocumentId | ||
Line 185: | Line 209: | ||
<br/> | <br/> | ||
The parentDocumentId can be formatted using the following XPath expression, where '''$docID''' in the expression below represents the identifier.<br/>concat($docID/@root,"<nowiki>^</nowiki>", $docID/@extension) | The parentDocumentId can be formatted using the following XPath expression, where '''$docID''' in the expression below represents the identifier.<br/>concat($docID/@root,"<nowiki>^</nowiki>", $docID/@extension) | ||
+ | | | ||
|- | |- | ||
|patientId | |patientId | ||
Line 192: | Line 217: | ||
|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: | |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: | ||
<br/>$patID <nowiki><</nowiki>= /ClinicalDocument/recordTarget/<br/>patientRole/id | <br/>$patID <nowiki><</nowiki>= /ClinicalDocument/recordTarget/<br/>patientRole/id | ||
+ | | | ||
|- | |- | ||
|practiceSettingCode | |practiceSettingCode | ||
Line 198: | Line 224: | ||
|align = "center"|CAD | |align = "center"|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. | |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 | |practiceSettingCodeDisplayName | ||
Line 204: | Line 231: | ||
|align = "center"|CAD | |align = "center"|CAD | ||
| This element shall contain the display names associated with the codes described above. | | This element shall contain the display names associated with the codes described above. | ||
+ | | | ||
|- | |- | ||
|serviceStartTime | |serviceStartTime | ||
Line 212: | Line 240: | ||
<br/> | <br/> | ||
Times specified in clinical documents may be specified with a precision in fractional sections, and may contain a time zone offset. In the XDS Metadata, it can be precise to the second, and is always given in UTC, so the timezone offset if present must be added to the current time to obtain the UTC time. | Times specified in clinical documents may be specified with a precision in fractional sections, and may contain a time zone offset. In the XDS Metadata, it can be precise to the second, and is always given in UTC, so the timezone offset if present must be added to the current time to obtain the UTC time. | ||
+ | | | ||
|- | |- | ||
|serviceStopTime | |serviceStopTime | ||
Line 220: | Line 249: | ||
<br/> | <br/> | ||
Times specified in clinical documents may be specified with a precision in fractional sections, and may contain a time zone offset. In the XDS Metadata, it can be precise to the second, and is always given in UTC, so the timezone offset if present must be added to the current time to obtain the UTC time. | Times specified in clinical documents may be specified with a precision in fractional sections, and may contain a time zone offset. In the XDS Metadata, it can be precise to the second, and is always given in UTC, so the timezone offset if present must be added to the current time to obtain the UTC time. | ||
+ | | | ||
|- | |- | ||
|sourcePatientId | |sourcePatientId | ||
Line 228: | Line 258: | ||
<br/> | <br/> | ||
The patientId can be formatted using the following XPath expression, where '''$patID''' in the expression below represents the appropriate identifier.<br/>concat($patID/@extension,"<nowiki>^^^</nowiki>&", $patID/@root, "&ISO") | The patientId can be formatted using the following XPath expression, where '''$patID''' in the expression below represents the appropriate identifier.<br/>concat($patID/@extension,"<nowiki>^^^</nowiki>&", $patID/@root, "&ISO") | ||
+ | | | ||
|- | |- | ||
|sourcePatientInfo | |sourcePatientInfo | ||
Line 236: | Line 267: | ||
<br/> | <br/> | ||
The sourcePatientInfo metadata element can be assembled from various components of the patientRole element in the clinical document. | The sourcePatientInfo metadata element can be assembled from various components of the patientRole element in the clinical document. | ||
+ | | | ||
|- | |- | ||
|title | |title | ||
Line 242: | Line 274: | ||
|align = "center"|SA | |align = "center"|SA | ||
|/ClinicalDocument/title | |/ClinicalDocument/title | ||
+ | | | ||
|- | |- | ||
|typeCode | |typeCode | ||
Line 250: | Line 283: | ||
<br/> | <br/> | ||
The typeCode should be mapped from the ClinicalDocument/code element to a set of document type codes configured in the affinity domain. One suggested coding system to use for typeCode is LOINC, in which case the mapping step can be omitted. | The typeCode should be mapped from the ClinicalDocument/code element to a set of document type codes configured in the affinity domain. One suggested coding system to use for typeCode is LOINC, in which case the mapping step can be omitted. | ||
+ | | | ||
|- | |- | ||
|typeCodeDisplay<br/>Name | |typeCodeDisplay<br/>Name | ||
Line 256: | Line 290: | ||
|align = "center"|CADT | |align = "center"|CADT | ||
|/ClinicalDocument/code/@displayName | |/ClinicalDocument/code/@displayName | ||
+ | | | ||
|- | |- | ||
|uniqueId | |uniqueId | ||
Line 264: | Line 299: | ||
<br/> | <br/> | ||
The uniqueId can be formatted using the following XPath expression, where '''$docID''' in the expression below represents the identifier.<br/>concat($docID/@root,"<nowiki>^</nowiki>", $docID/@extension) | The uniqueId can be formatted using the following XPath expression, where '''$docID''' in the expression below represents the identifier.<br/>concat($docID/@root,"<nowiki>^</nowiki>", $docID/@extension) | ||
+ | | | ||
|- | |- | ||
|} | |} |
Revision as of 10:05, 21 March 2010
针对XDS、XDM和XDR的医疗文档绑定
这种绑定(binding)规定的是一种转换机制(transformation)。在存在来自其他来源的某份医疗文档以及信息的情况下,这种转换机制所产生的是来自XDS、XDM和XDR概貌的适当交易的XDS文档条目元数据(XDSDocumentEntry)要素。医疗文档(medical document,医疗文书)指的是存储在某个储存库(repository)之中并将在注册库(registry)之中加以引用的文档。其他信息来源包括文档来源角色(Document Source actor)的配置、共享域、地点或设施、本地协议、注册库/储存库之中的其他文档以及这份内容概貌。
在许多的情况下,CDA文档的创建针对的是特定共享域(affinity domain)之内不同的共享目的。在这些情况下,CDA的语境与共享域的语境并无两样;此时,必须运用下列映射关系。
在其他情况下,CDA文档可能是事先已经为内部用途而创建的,而后来又要加以共享。在这些情况下,CDA的语境并不一定会与共享域的语境相符。因此,下列映射关系此时并不一定会适用。
请注意如下表格之中所给出的具体细节。
XDS文档条目元数据
XDSDocumentEntry Attribute | XDS文档条目属性中文名称 | 可选程度 | 来源类型 | 来源/取值 | 来源/取值中文说明 | |
---|---|---|---|---|---|---|
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 | 条目UUID | 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 | MIME类型 | 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
|
XDS提交集元数据
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.
XDS提交集的使用
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.
XDS文件夹的使用
No specific requirements identified.
配置
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.