ISO 10159:2011
(Main)Health informatics — Messages and communication — Web access reference manifest
Health informatics — Messages and communication — Web access reference manifest
ISO 10159:2011 specifies the format of a manifest of web access reference pointers, 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 from a source clinical domain to a target clinical domain in which the server references are different from those in the source clinical domain.
Informatique de santé — Messages et communication — Manifeste de référence d'accès à Internet
General Information
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 10159
First edition
2011-12-15
Health informatics — Messages and
communication — Web access reference
manifest
Informatique de santé — Messages et communication — Manifeste de
référence d'accès à Internet
Reference number
ISO 10159:2011(E)
©
ISO 2011
---------------------- Page: 1 ----------------------
ISO 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 mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's 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 copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2011 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 10159:2011(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International 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 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 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 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.
© ISO 2011 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO 10159:2011(E)
Introduction
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 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 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 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 clinician 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 target 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 clinicians 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. 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 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 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 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
computational 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 in the target
computational domain.
iv © ISO 2011 – All rights reserved
---------------------- Page: 4 ----------------------
ISO 10159:2011(E)
The 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 objects 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 document;
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 the 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 computational 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 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 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 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 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.
This 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 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 manifest. 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 references 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 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
© ISO 2011 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO 10159:2011(E)
the 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 expresses a logical data structure.
vi © ISO 2011 – All rights reserved
---------------------- Page: 6 ----------------------
INTERNATIONAL STANDARD ISO 10159:2011(E)
Health informatics — Messages and communication — Web
access reference manifest
1 Scope
This International Standard specifies the format of a manifest of web access reference pointers, 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 from 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 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 the 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 purposes 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 commun
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.