1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationBS ISO 10159:2011Health informatics Messagesand communication Webaccess reference manifestBS ISO 10159:2011 BRITISH STANDARDNational forewordThis British Standard is the UK imple
2、mentation of ISO 10159:2011.The UK participation in its preparation was entrusted to TechnicalCommittee IST/35, Health informatics.A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purport to include all the necessaryprovisions
3、 of a contract. Users are responsible for its correctapplication. The British Standards Institution 2012ISBN 978 0 580 66611 7ICS 35.240.80Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the authority of theStandards Policy an
4、d Strategy Committee on 31 January 2012.Amendments issued since publicationDate T e x t a f f e c t e dBS ISO 10159:2011Reference numberISO 10159:2011(E)ISO 2011INTERNATIONAL STANDARD ISO10159First edition2011-12-15Health informatics Messages and communication Web access reference manifest Informati
5、que de sant Messages et communication Manifeste de rfrence daccs Internet BS ISO 10159:2011ISO 10159:2011(E) COPYRIGHT PROTECTED DOCUMENT ISO 2011 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mec
6、hanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.i
7、so.org Published in Switzerland ii ISO 2011 All rights reservedBS ISO 10159:2011ISO 10159:2011(E) ISO 2011 All rights reserved iiiForeword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing Intern
8、ational Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with
9、 ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of technical
10、 committees is to prepare International Standards. Draft International Standards adopted by the technical committees are circulated to the member bodies for voting. Publication as an International Standard requires approval by at least 75 % of the member bodies casting a vote. Attention is drawn to
11、the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO 10159 was prepared by Technical Committee ISO/TC 215, Health informatics. BS ISO 10159:2011ISO 10159:2011(E) iv ISO 201
12、1 All rights reservedIntroduction Web access technology is increasingly being used to enable clinicians to share clinical documents, including the results of healthcare procedures such as diagnostic imaging procedures, which can reference image data objects. This can be supported by means of one or
13、more document and data object repositories which enable clinical documents, and any data objects that they reference, to be made available to authorized clinicians who are subject to the same governance rules regarding access to such clinical documents and referenced data objects. A clinician might
14、wish to make clinical documents available to other clinicians whose systems have access to the servers to which his or her system has access. Several different use cases exist regarding the way in which a clinical document, in the form of e.g. a web page, can be made available by a source clinician
15、to clinicians within a target computational domain in such a way that any objects referenced by the clinical document can be retrieved and presented to the target clinicians. Different use cases exist, depending on whether or not the target clinicians reside in the same computational domain as the c
16、linician who wishes to share documents, which determines whether or not the target clinicians have access to the same servers as the source clinician. The following are some examples. a) The clinicians work in the same computational domain. The source clinician makes the document available to the ta
17、rget domain clinician by making a pointer to the clinical document available to them. The systems used by the target clinicians can display the clinical document text content and any referenced data objects since they have access to the same servers as the source clinician. b) The target domain clin
18、icians work in another computational domain with indirect access to the originating computational domain servers by means of agreed mechanisms. The clinician in the originating computational domain makes the document available to the target clinicians by means of a pointer to the clinical document.
19、The system used by the target clinician can display the clinical document text content and the referenced objects since it has indirect access to the servers referenced by the pointers within the document by agreed means. c) The target clinicians work in another computational domain within which no
20、access to the originating computational domain servers has yet been implemented. In this case, the clinical document can be made available to the target clinicians so that the data objects and clinical document text can be displayed in similar ways to those available in the originating computational
21、 domain only by sending copies of the clinical document and referenced objects to the target computational domain where they are stored in target computational domain servers. Since the pointers in the clinical document point to servers that are not accessible in the target computational domain, the
22、 system that receives the copy files in the target computational domain will be unable to display the referenced files unless some appropriate provisions are made. There are two possibilities: 1) the pointers in the clinical document are changed to point to the appropriate servers in the target comp
23、utational domain; 2) the clinical document cannot be changed since it has been digitally signed and requires that a mechanism be implemented to enable the pointers to be changed in real time, i.e. some mechanism to detect pointers that will fail and replace them with the appropriate pointers for use
24、 in the target computational domain. BS ISO 10159:2011ISO 10159:2011(E) ISO 2011 All rights reserved vThe provisions of this International Standard provide a logical data structure that can support a solution in the case of c) 2) above, in which the original document and the referenced information o
25、bjects stored in files are sent to the target computational domain together with a manifest of referenced information objects. This manifest consists of a table with one row per referenced object, which includes columns for certain key information as follows: the URI as it appears in the original do
26、cument; the Globally Unique Identifier of the information object to be used in the source computational domain (see 3.1.5); the Globally Unique Identifier of the information object to be used in the target computational domain; the name of the information object; the name of the file that contains t
27、he information object; a security text string containing references to security policies for the control of access to the document, as agreed by the communicating parties; a checksum of the content of the file; the URI to be used in the source computational domain; the URI to be used in the target c
28、omputational domain, when known; a patient identifier to be used in the target computational domain. Applications in the target computational domain could work in such a way that the URIs within the document are changed from that in the original document to the appropriate value before being sent on
29、 to the network. This can be done by looking up the URI value in column 7 of the manifest found in the row having a column 1 URI value equal to the one stored in the original document. Those URIs in documents that have been created in the target computational domain do not have entries in a manifest
30、 and are sent unchanged. This functionality could be incorporated within the server application. The standard provisions can be used to enable sharing of documents that are referenced by an IHE XDS Document Registry without the need for further provisions, since referenced data objects are retrieved
31、 directly from the server. The method of using the information in the manifest to overcome the problem of broken links in a particular situation is outside the scope of this International Standard. It is important that institutions adapt their procedures in the way which is most appropriate for them
32、 to manage the sharing of documents and information objects referenced by them between different computational domains. The maintenance of the locally stored copies of manifest content could be enabled through the use of the demographics information contained in the header section of the manifest. T
33、his International Standard presumes that the enabling governance agreements and mechanisms to allow sharing of manifests (and their embedded URIs) have already been established. The methods described here are simply for the purpose of ensuring that “packages” of related documents can be copied to a
34、target destination and the original URIs in the referencing document can be redirected to the target URIs in the target computational domain. It should be understood that the original URIs are not used in the target domain. The source domain will, of course, not fill in the target items of the manif
35、est. It should also be understood that the transformation of the source domain URIs to the target domain URIs does not necessarily require the target URIs be stored in the manifest. It is anticipated that the manifest could constitute a source of traceability for the transformation of the URI refere
36、nces from source to target. If the target URIs are recorded in the manifest after the transformation, then the content of the manifest can be used to assist in addressing any problems of access or presentation that arise during use in the target domain. In this case, the manifest is not a temporary
37、object, but something retained for these purposes and the recording of the destination URIs is helpful. It is also the case that a method for handling the translation of URIs could depend on a persistent manifest. It is necessary to support BS ISO 10159:2011ISO 10159:2011(E) vi ISO 2011 All rights r
38、eservedthe case that it is not possible to amend the original referencing document, e.g. if it has been digitally signed. Should the target organization have other methods for traceability of the transformation, then of course the destination manifest need not persist. This International Standard ex
39、presses a logical data structure. BS ISO 10159:2011INTERNATIONAL STANDARD ISO 10159:2011(E) ISO 2011 All rights reserved 1Health informatics Messages and communication Web access reference manifest 1 Scope This International Standard specifies the format of a manifest of web access reference pointer
40、s, information object identifiers, information object filenames and associated information required by a target IT system. This enables local web access to the referenced information objects when a package containing the referencing document, the manifest and the objects (stored in files) is sent fr
41、om a source clinical domain to a target clinical domain in which the server references are different from those in the source clinical domain. The following topics are outside the scope of this International Standard: technologies used for data storage and communication; support for the traceability
42、 of the transformation of the URI references from source to target in the case of sending of files received by a target IT system to another clinical domain. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only t
43、he edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO 18232, Health informatics Messages and communication Format of length limited globally unique string identifiers 3 Terms, definitions and abbreviations For the purp
44、oses of this document, the following terms, definitions and abbreviations apply. 3.1 Definitions 3.1.1 information object well-defined piece of information, definition, or specification which requires a name in order to identify its use in communication NOTE Adapted from ISO/IEC 8824-1. 3.1.2 object
45、 identifier value, distinguishable from all other such values, which is associated with an information object NOTE Adapted from ISO/IEC 8824-1. BS ISO 10159:2011ISO 10159:2011(E) 2 ISO 2011 All rights reserved3.1.3 data object identifier sequence of integer components, constructed as specified in IS
46、O/IEC 8824-1, which has a root sequence of components issued by a national standards body and a sequence of following integer components whose uniqueness is guaranteed by the organization which defined it NOTE The root sequence of components is guaranteed to be globally unique by that national body
47、registered as specified by ISO/IEC 9834-8. 3.1.4 unique identifier identifier which is different from any other such identifier within a given namespace 3.1.5 globally unique identifier identifier that is different from any other such identifier in any clinical domain namespace 3.1.6 globally unique
48、 string identifier alphanumeric string with a maximum length of 64 characters, which is different from any other alphanumeric string that has been or will be exchanged according to the provisions of this International Standard 3.1.7 computational domain a domain within which all IT systems can acces
49、s the same set of servers 3.2 Abbreviated terms GUSI Globally Unique String Identifier, as specified in ISO 18232 URI A string of characters used to identify a resource on the Internet 4 Manifest logical data format 4.1 Manifest header 4.1.1 Identification information The following information shall be included within the header section of the manifest in order to uniquely identify the document source, and the subject of care: document source organisation identification; document repository identificati
