DD ISO/TS 27790:2009

Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviated terms
5 Document registry framework
Annex A (informative) - Korean National Extension to IHE IT
        Infrastructure Technical Framework CDA Document
        Separation - XDS Extension
Bibliography

Describes a general-purpose document registry framework for transmitting, storing and utilizing documents in clinical and personalized health environments.

This Technical Specification specifies a general-purpose document registry framework for transmitting, storing and utilizing documents in clinical and personalized health environments. It is quite broad in its applicability to realise the goal of sharing health-related documents spanning a broad spectrum of health domains such as healthcare specialities covering laboratory, cardiology, eye care, etc. and the many areas of personalized health. This web services-based registry framework includes a document registry and associated repository to allow the sharing of any form of health documents including HL7 CDA (clinical document architecture). It specializes in health, W3C Web Services Standards, ISO15000 (ebXML registry standards) and OASIS ebXML Registry Information Model 3.0 through the use of the IHE Cross-Enterprise Document Sharing (XDS) from the Integrating the Healthcare Enterprise (IHE) Information Technology Infrastructure (ITI) technical framework, quoting from the Cross-Enterprise Document Sharing (XDS) Profile: “The Cross-Enterprise Document Sharing IHE Integration Profile facilitates the registration, distribution and access across health enterprises of patient and citizen electronic health records. Cross-Enterprise Document Sharing (XDS) is focused on providing a standards-based specification for managing the sharing of documents between all health enterprises, ranging from private physician offices to clinics to acute care in-patient facilities to personal heath record systems. The XDS IHE Integration Profile assumes that these enterprises belong to one or more affinity domains. An affinity domain is a group of healthcare enterprises that have agreed to work together using a common set of policies and that share a common registry infrastructure.” This Technical Specification also supports document registration and retrieval via the federation of documents’ registries (see IHE Cross-Community Access) in terms of individual users to reduce health information extrusion possibilities. This Technical Specification supports the sharing of documents of any standardized content in the context of healthcare and well-being. It describes the means of locating and accessing documents among a diverse set of health organizations. It is designed for leverage of existing health informatics for structuring and semantically rich health information, if so desired. It does not require the development of new health informatics standards. This Technical Specification also references a number of companion standards-based specifications that offer optional extensions to enhance the basic capabilities offered by IHE XDS, as listed below. An XDS extension supporting the fragmentation of the content of the documents into two parts: a header fragment and a body fragment. This separation scheme enhances confidentiality because the gathering of both header and body and their relational information involves cracking into multiple repository servers. This has been developed as an IHE Korean Extension on the IHE XDS Profile. NOTE1 The incremental effectiveness achieved by header/body separation will have to be re-evaluated once the effectiveness of the security solutions to protect data at rest (e.g. encryption) has been finalized. A series of security- and privacy-related IHE profiles, such as Patient Identification Cross-Referencing (PIX), Patient Demographics Query (PDQ), Basic Patient Privacy Consent (BPPC), and Cross-Enterprise User Assertion (XUA). NOTE2 The use of IHE Audit trail and Node Authentication (ATNA) as well as Consistent Time (CT) is required as part of IHE XDS. These Profiles are therefore not listed above.