Difference between revisions of "PCC TF-2/Bindings/zh"
| (3 intermediate revisions by the same user not shown) | |||
| Line 96: | Line 96: | ||
======XDS文档条目格式代码（XDSDocumentEntry.formatCode）====== | ======XDS文档条目格式代码（XDSDocumentEntry.formatCode）====== | ||
| − | + | XDS文档条目格式代码XDSDocumentEntry.formatCode必须为 '''urn:ihe:lab:xd-lab:2008''' 。格式代码formatCode的编码系统codeSystem必须为1.3.6.1.4.1.19376.1.2.3。 | |
=====XDS提交集（XDSSubmissionSet）===== | =====XDS提交集（XDSSubmissionSet）===== | ||
| − | + | 无额外的约束。详情请参见PCC-TF-2 第5.1.1.1.2小节 或者 [[PCC_TF-2/Bindings/zh]]. | |
=====XDS文件夹（XDSFolder）===== | =====XDS文件夹（XDSFolder）===== | ||
| − | + | 无额外的约束。详情请参见PCC-TF-2 第5.1.1.1.3小节 或者 [[PCC_TF-2/Bindings/zh]]。 | |
Latest revision as of 10:17, 26 March 2010
IHE病人医疗护理服务协调绑定（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 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. These concepts are universal to XDS, XDR and XDM.
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.
针对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.
来自其他领域的扩展（Extensions from other Domains）
扫描型文档（Scanned Documents）(XDS-SD)
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.
XDS文档条目（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
XDS文档条目格式代码（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.
XDS文档条目唯一标识符（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.
XDS-SD文档实例的关联（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.
XDS提交集（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.
XDS文件夹（XDSFolder）
No additional requirements. For more information, see PCC-TF-2 Section 5.1.1.1.3 or PCC_TF-2/Bindings.
基本病人隐私知情同意书（Basic Patient Privacy Consents，BPPC）
实验室检验报告（Laboratory Reports）(XD-LAB)
XD-Lab 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.
XDS文档条目（XDSDocumentEntry）
XD-Lab 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
XDS文档条目事件代码列表（XDSDocumentEntry.eventCodeList）
XD-Lab documents further constrain the the XDSDocumentEntry.eventCodeList to the following.
| Attribute | Optional? | Source Type | Source/ Value |
|---|---|---|---|
| eventCodeList | R2 | SAT | ClinicalDocument / component / structuredBody / component / section / entry / act / entryRelationship / organizer (templateId="1.3.6.1.4.1.19376.1.3.1.1")/ component / observation(templateId="1.3.6.1.4.1.19376.1.3.1.1.1")/code
AND ClinicalDocument / component / structuredBody / component / section / entry / act / subject / code If the document has Reportable Condition, then this code shall be among those listed in the eventCodeList. Additionally, if the document contains information about a Non-Human Subject, then the code that indicates what this subject is shall be among those listed in the eventCodeList. Thus, this attribute has been enhanced from the XDS profile from O to R2. |
XDS文档条目格式代码（XDSDocumentEntry.formatCode）
XDS文档条目格式代码XDSDocumentEntry.formatCode必须为 urn:ihe:lab:xd-lab:2008 。格式代码formatCode的编码系统codeSystem必须为1.3.6.1.4.1.19376.1.2.3。
XDS提交集（XDSSubmissionSet）
无额外的约束。详情请参见PCC-TF-2 第5.1.1.1.2小节 或者 PCC_TF-2/Bindings/zh.
XDS文件夹（XDSFolder）
无额外的约束。详情请参见PCC-TF-2 第5.1.1.1.3小节 或者 PCC_TF-2/Bindings/zh。