Implementation guide for document sources | Norwegian usage of IHE XDS XCA and XUA

Table of contents

• Section 1: Profiles and requirements
• Section 2: Administration of document source
• Section 3: Integration and testing
• Section 4: Transactions and search parameters
• Section 5: Norwegian profile for XDS metadata

Section 1: Profiles and requirements

Introduction

Patient Health Records (PHR) facilitates Cross enterprise document sharing between health professionals and between health professionals and citizens in Norway.
The main objectives of PHR are:

• Give health professionals necessary access to referrals, discharge summaries and other types of reports(documents) stored in other healthcare enterprises to achieve more effective health care decisions and reduce errors.
• Reduce the administrative burden and costs of today's collection and delivery of health information.
• Increase the overview of available health information across enterprises.
• Enable access to patients to their medical records throughout Norway.

To facilitate the sharing of health records in the Norwegian health care, interoperability between each actor is mandatory. The goal of this document is to achieve a common understanding of how profiles and standards must be implemented to achieve this. The target audience of this document is technical professionals wanting to implement a solution for making healthcare information available cross-enterprise.

Normative references

• IT Infrastructure (ITI) Technical Framework Volume 1
• IT Infrastructure (ITI) Technical Framework Volume 2
• Metadata used in Document Sharing profiles (ITI TF Vol. 3)
• Norwegian profiling of IHE XDS metadata
• NDH | Målarkitektur for nasjonal dokumentdeling

Non-normative references

• SAML-specification | NHN Utviklerportal
• Begrepsliste | NHN Utviklerportal

About this document

This document will describe the Norwegian usage and profilings of the IHE integration profiles based on XDS, XCA and XUA provided in Volumes 1 through 3 of the IHE IT Infrastructure Technical Framework in a national context.

Profilings are the extensions and restrictions to actors and transactions in the profiles. The national extensions and restrictions are included to effectively support document sharing in healthcare in Norway.

IHE and IHE profiles

Integrating the Healthcare Enterprise (IHE) is an initiative by healthcare professionals and industry to improve the way computer systems in healthcare share information. (IHE)-profiles describe the interactions between different systems, but does not describe what should be integrated in those systems.
The word profile is used in the context of "shape", as in a profile has a certain shape, but what makes up that shape (ie. the details) are not specified. This gives the implementer the freedom to "fill up" the shape with what they desire, as long as the end result of the shape stays the same. In practical terms, this gives the implementer enough freedom to ensure compliancy with their systems, but the profiles are also sufficiently described as to ensure interoperability with other systems.

Aspects of profiles that IHE does not cover include:

• Roles and responsibilities
• Privacy concerns
• Authorization
• When the publication of a document occurs, and what is published
• Administrative roles
• Configurations
• Service-Level Agreements (SLA)

To begin integration as a document source for Patent Health Records, it is important for the reader to familiarize themselves with the concept of an Affinity Domain, aswell as the profiles XDS, XCA, XUA and their respective transactions (ITI-messages).

IHE profiles for storing documents

IHE has described profiles for various interactions between healthcare systems. The Provide and Register Document Set-b ITI-41 profile is relevant for saving/storing documents.
It is up to the document source themselves to establish a mechanism for storing documents. This may be based on the ITI-41 profile, but other approaches are valid as long as the formats and metadata-elements follow specifications.

National adaptions of IHE profiles

Below is a description of the national considerations taken when PHR (formerly "document sharing") was being established as a national service. These considerations were done in relation to the national amenities in place, such as a National Patient Identifier(NPI/NIN).
When identifying a patient, the XDS profile specifies the actor Patient Identity Source, as specified in ITI-TF Volume 1 chapter 10.1. In the norwegian use of IHE XDS, the Patient Identity Source has been omitted in favor of the NPI for identification of a given patient.

As the need for identifying patients based on local identifiers are not required, another decision was to utilize a central, national XCA-gateway (maintained by Norsk helsenett) for centralized querying and retrieval of documents. This means that all queries to PHR goes through the national XCA, and the national XCA acts as a forwarder to the document sources. Norsk helsenett administrates the service on a national level.

Optimized queries

Note: As of writing, this is not in use. It is described here for informational purposes.

Use of IHE XCA requires an Initiating Gateway to always send document queries to every existing responding gateway. South-Eastern Norway Regional Health Authority covers about half the population in Norway. It is probably not effective to send all queries to all communities. And since our document sharing architecture is not including a national master patient index register, holding information on where to find patients' documents, other measures to optimize queries must be evaluated. A possible solution is to use the IHE standard Cross-Community Patient Discovery (IHE XCPD). IHE XCPD supports the means to locate communities that hold patient relevant health data across communities. The Cross Gateway Patient Discovery transaction ITI-56 supports the ability for Initiating Gateways to request a list of communities which may have healthcare data about the identified patient.

Description of usage of IHE XCPD

When an Initiating Gateway receives a document query (ITI-18) for a given patient, it requests all Responding Gateways with an ITI-56 Patient Location Query. Each Responding Gateway must work out whether they have any health data about the requested patient and send a negative or positive response back to the Initiating Gateway. The Initiating Gateway will make a list of communities responding positively, and then send an ITI-38 to these communities. When acquiring/implementing a Responding Gateway, communities should ensure that the solution supports processing an ITI-56 Patient Location Query.

Actors and components

The XDS-architecture consists of the following actors/components:

Document source

A document source is typically an EHR-system which has produced a document which will be shared using the XDS-solution.

Document consumer

A document consumer is typically a EHR-system or (citizen portal) which queries for documents on a given patient.

Patient identity source

This component ensures every patient is given an unambigous identificator, for example a local, regional or nationwide population register. In Norway, a personal identificator is in use (person number), so a dedicated service for handling patient identifications is not required.

Document repository

A document repository is the service responsible for storing or making the document accessible. an XDS-solution can consist of one or more document repositories.

Document registry

The document registry contains information (metadata) about all archived documents in the XDS area served by this document repository. An XDS site is always served by only one document repository, but a document repository can cover multiple XDS areas. In addition to metadata about existing documents, the document register contains pointers to the document archive where the document is stored.

Affinity Domain

The concept of an affinity domain is, literally and figuratively, central in the realm of sharing health documents. The XDS-profile describes how documents are shared across enterprise boundaries within an affinity domain, as well as the rules that make sharing possible. An affinity domain has its own unique identifier, known as a homeCommunityID. This ID is used when querying the domain.
The boundaries of an Affinity Domain is not specified, but a logical separation within a country is natural. In Norway, this separation is on a RHF (Regionalt helseforetak)-level. This level of separation makes it possible for the affinity domains to profilings catered towards the needs of both the domain, aswell as the RHF.

Transactions in XDS

A set of transactions that can be performed in an XDS solution has been The technical format of the transactions is defined according to the ebXML RegRep 3.0 specification. The various transactions are briefly described below:

Send (Provide and Register Document Set - ITI-41)

This transaction is used to send relevant documents from a document source to a document archive aswell as the document metadata.

Register (Register Document Set - ITI-42)

This transaction is used to send information about new documents in a document archive from this document archive to a document register covering the relevant area. Similar to send, but here only the metadata is sent, and not the actual document.

Search Registry (Registry Stored Query - ITI-18)

This transaction is used in a dialogue between the document user and the document register to ask for documents with specific properties and to get answers to which documents exist and where the individual document is located. A request with specific search parameters is sent from a document user to the document register, which sends back a list of documents that satisfy the search parameters.

Get (Retrieve Document Set - ITI-43)

This transaction is used by a document user to transfer one or more documents from a document repository. A request with specific document identifiers is sent from a document user to a document repository that is tasked with retaining the requested documents. The document archive sends the requested documents back to the document user.

Update patient identity feed information (ITI-8)

This transaction is used in a dialogue between the document register and the patient identity source to exchange information about the used patient identifier.

Document consuming process

Below is a diagram showing the process of retrieving the document-list and the document. Each affinity domain has its own XCA, which again has its own registry and repositories.
When querying for a document-list, the registry is utilized, as it holds the metadata and references to the documents in the repository. When retrieving a document, the repository is used with the ID from the registry.

Diagram 1: Simplified example on a query of document, each XCA is its own affinity domain, and the response for each domain may be different (ie. some domains reject requests from certain GP-roles)

Object Identifiers (OID)

Note: For OIDs to effectively work, there must be some level of governance when creating and managing OIDs. Norsk helsenett(NHN) should have a comprehensive overview of the OIDs related to PHR. NHN shall be informed of the OID of a new document source.

Object Identifiers are unique identifiers for objects or things. Anything can have an OID. In PHR, OIDs are used to unambiguously identify a system or facility. The OIDs might get translated by the systems into the actual URL, which means the URL can change, but the OID stays the same. OIDs are also used in logging. OIDs have a "tree/path"-like structure, and can be represented by its numerical or text variant.
More about OIDs on NHN's Developer portal (In Norwegian).

Governing Object Identifiers

The Norwegian profile of IHE XDS metadata defines the use of OIDs for identifying communities. Norsk helsenett (NHN) governs an OID-base and can issue an OID to a community. Each Norwegian health region also governs their own OIDbase and can choose to issue their own homecommunity ID. The OID-base which NDE governs has the following OID structure for document sharing:

• 2.16.578.1.12.4.1.7 – Document sharing root
  • 2.16.578.1.12.4.1.7.1 – Community base OIDs governed by NHN
    • 2.16.578.1.12.4.1.7.1.1 – National community

Historically, this OID-base has belonged to The Norwegian Directorate of eHealth (NDE/e-Helse) for PHR (formely known as Dokumentdeling)

Section 2: Administration of XDS-infrastructure for document sources

The administration include the management of the service after it is in production.

Routines for administration

It is important that any actor in PHR follows the administration routines. This is to ensure that incidents and processes are followed in the same manner. See Deling av pasientens journaldokumenter, section Spesielle bruksvilkår for Pasientens journaldokumenter* og forvaltningsrutiner (NB: In norwegian)

Administration of the document registry

The metadata in the document registry must be maintained to ensure the information is accessible. This can be done by a document administrator. They must be capable of searching the metadata, aswell as updating the information in the registry. This will require its own interface and accesses.

Administration of document ownership

There are multiple scenarios in which the document source has to make changes to their organization or system that affects the access to their stored documents. Some of these cases are:

1. A general practitioner who shares documents concludes their practice or switches EHR (Electronic Health Record) providers.
2. When an organization intends to replace or merge its document repository solution or transfer its responsibilities to another organization.
3. If an organization upgrades or changes its entire system platform, such as transitioning from an older version to a newer one, it can impact document links in terms of accessibility and compatibility.
4. In the event of business mergers or divestitures, there may be a need to review and update document links to reflect the new organizational structures and responsibilities.

Architectural principles

This section will cover business, informational and security-realted principles for document sources.

Business-principles

Information principles

Security principles

Section 3: Integration and testing

This section aims to give the actor (hereunder document source/ techical personell/integrator) sufficient information to be able to integrate and test their integration with Patients Health Records.
While the previous section has covered the basics of the standards, interactions and processes involved in creating and managing documents, this section will focus on the practical steps to integrating with PHR as a document source.

Environments

It is recommended that the actor follows the integration process linearly, beginning with Dev-environment, then Test, followed by QA and then Production. Integrations may begin in the test-environment if the actor does not have development environment.

Integration and workflow

For sharing/publishing documents, the Provide and Register Document Set-b (ITI-41) transaction is used. Implementors of this transaction shall comply with all requirements described in: ITI TF-2: Appendix V : Web Services for IHE Transactions.
Document sources need a mechanism for making a document-list available to the requestor. This mechanism should follow the IHE-profiles and specifications. Each community/document source must be compliant to the Norwegian profile of IHE XDS.b metadata With reference to chapter 3.38 Cross Gateway Query in IHE ITI-2b, the following restriction applies for Norwegian use of XDS:

National document sharing does not require support of Associations, folders and submission sets . A responding gateway can respond with zero entries when receiving queries which specifies associations, folders or submission sets

Establish an XCA gateway

In practical terms, and XCA-gateway is a SOAP-endpoint capable of recieving and processing SOAP-requests. The requests a document source will recieve is ITI38 and ITI39 - messages, and they shall respond with a corresponding message of the same type.

• For ITI-38-messages, the Content-Type shall be application/soap+xml
• For ITI-39-messages, the Content-Type shall be multipart/related

Actors who already use DIPS (Classic or Arena) can aquire DIPS IHE XDS. This also requires the DIPS Service Broker-platform. To handle SAML-tokens for DIPS-based integrations, DIPS Federation Service (authentication), DIPS Authorization Service (authorication) og DIPS Audit Service (logging) must also be in place.

Diagram 2: Transactions between national and regional XCA-gateways

SOAP message restrictions

ITI-43 Retrieve Document Set and XCA ITI-39 Cross Community Retrieve transactions require SOAP 1.2 with MTOM/XOP. When using SOAP 1.2 MTOM/XOP the following applies:

• Usage of a MTOM/XOP wrapper
• Metadata goes in the root part which is identified by the start parameter of the content-type header
• Documents are included by the Document element (as defined by the profile)
• For national usage only un-optimized format is supported. The document contents must be included as base64 encoded value of the Document element. ITI-18 and ITI-38 transactions require use of Simple SOAP message.

XDS Document Source Options

Section 3.41.4.1.2.1 of the ITI-41 transaction describes 4 options for document sources. None of these options are in use in document sharing today.

XCA Options supported

Table 18.2-1 in IHE ITI Vol 1 shows a list of possible options for XCA actors. In Norway only one option must be supported for each XCA community: XDS Affinity Domain Option (see chapter 18.2.1 in IHE ITI Vol 1 for more details). The other options are not supported. In addition, grouping rules described in chapter 18.2.3 in IHE ITI VOL 1 must be supported.

Ensure correct validation of user claims

When recieving a request, the document source must correctly process the SAML-ticket from HelseID. In other environments, there must be unanimous logic in place to ensure that only authorized healthcare providers are allowed to retrieve information. Non-standard access control should be documented. A common approach is to utilize a PEP/PAP/PDP service for this.

Ensure sufficient logging

Transaction-id

The IHE XDS and XCA profiles only specify logging details based on transactions between two IHE defined actors. Using XDS over XCA, many actors and transactions are involved in a query or retrieval request. IHE does not specify how to link each transaction belonging to the same query or retrieval request/response. This will depend on each software architecture and is therefore out of scope for IHE to specify.
Still, it is essential to link each transaction involved in the same request/response. The underlying standards used in IHE XDS/XCA/XUA has no mechanism to include an identifier which can be added in each transaction a query or retrieval request/response consists of.

Persistence of Transaction-IDs

The XCA-gateway will take the <MessageID>-xml element in the SOAP-message and use it as a session-ID. Example:
<MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:02d9e81f-f6ee-42df-b264-f70cdae5c706</MessageID>.
The XCA-gateway will also create session-IDs which will be used by the responding gateways and as their "local" session ids.

Diagram 3: Delegation of session IDs

This all happens in the same session-ID initially delegated by the consumer, which makes tracing events across gateways possible.

Document formats

A document can have different formats: xml, pdf, tiff etc. To show a document to the user a Document Consumer must recognize the format to select a viewer able to understand the format. Combinations of the metadata attributes MimeType and FormatCode shall give enough information for Document Consumers to choose a correct viewer. Examples of valid combinations is shown in the following section.

It is recommended to use XML based document formats since these documents are machine readable.

XML-based document formats

Several XML-based message standards are mandatory to use in Norway. Documents based on these standards should be shared in xml-formats, and stylesheets for displaying these XML formats are published on Sarepta.ehelse.no.

⚠️⚠️ Legg ut stylesheets på utviklerportalen ⚠️⚠️

Example on usage:

• Filetype: XML
• MimeType: application/xml
• FormatCode: urn:no:ehelse:xmlstds:henvisning:2017-11-30

CDA based document formats

CDA is a HL7 standard for static clinical documents. CDA is not used on a national level in Norway today and usage of CDA documents must therefore be avoided. In the future, national usage of CDA based clinical documents will probably need to be supported.

CDA wrapper for non-XML documents

The CDA standard includes a technique to wrap an XML envelope around non-xml documents to add XML metadata to the document. Such a CDA document consists of a CDA header where metadata is placed and a CDA body where the non-XML document is included.
Wrapping non-XML documents like images, PDFs and RTFs in a CDA wrapper is allowed. When a CDA wrapper is used for non-XML documents, MimeType shall include the Mime type of the non-XML document and FormatCode shall specify usage of a CDA wrapper with version.

Example 1:

• Filetype: GIF
• MimeType: image/gif
• FormatCode: urn:hl7-org:sdwg:ccda-nonXMLBody:2.1

Example 2:

• Filetype: PDF
• MimeType: application/pdf
• FormatCode: urn:hl7-org:sdwg:ccda-nonXMLBody:2.1

Metadata in the CDA header is currently not profiled for use in Norway and it is up to each document repository to decide which metadata to include.
When displaying non-XML documents, it is common to show some of the document's metadata in the same display. Although metadata is included in the CDA header, we recommend using metadata from the ITI-18 response as these are standardized.

Diagram 4: Layer-view of the metadata in a ITI39/ITI43 response

Which document types can be shared

Theses are the basis for the document types which can be shared, and is excpected from other actors.

Testing the integration

When the endpoints are configured in the NHN-XCA, testing the application will be necessary to verify the functionality and compliancy of the document source. The test determines if it is possible to retrieve metadata and documents from the source, and if the data is correct.

Test-case | Integration - document source for Patient Health Records:

Section 4: Transactions and search parameters

This section will provide a brief description of the IHE transactions used in national document sharing, aswell as the search parameters for each transaction.

ITI-18 Registry Stored Query

ITI-18 Registry Stored Query transaction is a query done by either Document Consumer or XCA gateway against Document Registry to find documents with defined criteria.
Example:

<ns4:AdhocQueryRequest xmlns:ns4="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0">
    <ns4:ResponseOption returnType="LeafClass"/>
    <AdhocQuery id="urn:uuid:14d4debf-8f97-4251-9a74-a90016b0af0d">
        <Slot name="$XDSDocumentEntryPatientId">
            <ValueList>
                <Value>'12119000465^^^&2.16.578.1.12.4.1.4.1&ISO'</Value>
            </ValueList>
        </Slot>
        <Slot name="$XDSDocumentEntryStatus">
            <ValueList>
                <Value>('urn:oasis:names:tc:ebxml-regrep:StatusType:Approved')</Value>
            </ValueList>
        </Slot>
        <Slot name="$XDSDocumentEntryCreationTimeFrom">
            <ValueList>
                <Value>20230513000000</Value>
            </ValueList>
        </Slot>
        <Slot name="$XDSDocumentEntryCreationTimeTo">
            <ValueList>
                <Value>20240513235959</Value>
            </ValueList>
        </Slot>
    </AdhocQuery>
</ns4:AdhocQueryRequest>

ITI-18 specifies many different types of stored queries. For national use of ITI-18 only two stored queries are required to support for Document Consumers and XCA gateways:

• FindDocuments: Find documents in a document registry for a given patientID with a matching availabilityStatus attribute
• GetDocuments: Retrieve metadata on (a collection of) documents given unique Ids on the documents. Other stored queries defined in 3.18.4.1.2.3.7 in ITI TF-2a is optional and XCA communities not supporting these stored queries shall return a zero successful result.

Search parameters for stored query FindDocuments

ITI TF-2a specifies the query parameters for a stored query “FindDocuments” (see ITI TF-2a 3.18.4.1.2.3.7.1). The stored query “FindDocuments” MUST be used using the parameters described in Table 8.
In column 2 the cardinality of each parameter is described:

• [1..1] indicates that the parameter is required for the document consumer and only one value is allowed.
• [0..1] or [0..*] indicates that the parameter is optional for a document consumer, but when using the parameter one [0..1] or multiple [0..*] values are allowed.
• [0..0] indicates "not in use".

<rim:Slot name="$XDSDocumentEntryPatientId">
    <rim:ValueList>
        <rim:Value>
            12345612345^^^&2.16.578.1.12.4.1.4.1&ISO
        </rim:Value>
    </rim:ValueList>
</rim:Slot>

<rim:Slot name="$XDSDocumentEntryClassCode">
    <rim:ValueList>
        <rim:Value>
            'A00-1^^2.16.578.1.12.4.1.1.9602'
        </rim:Value>
    </rim:ValueList>
</rim:Slot>

<rim:Slot name="$XDSDocumentEntryClassCode">
    <rim:ValueList>
        <rim:Value>
            'A03-2^^2.16.578.1.12.4.1.1.9602'
        </rim:Value>
    </rim:ValueList>
</rim:Slot>

<rim:Slot name="$XDSDocumentEntryCreationTimeFrom">
<rim:ValueList>
    <rim:Value>200412252300
    </rim:Value>
</rim:ValueList>
</rim:Slot>

<rim:Slot name="$XDSDocumentEntryAuthorPerson"> 
 <rim:ValueList>
   <rim:Value>
        9144889^Koman^Magnar^^^^^^& 2.16.578.1.12.4.1.4.4&ISO  
   </rim:Value> 
  </rim:ValueList> 
</rim:Slot>

<rim:Slot name="$XDSDocumentEntry FormatCode "> 
    <rim:ValueList> 
        <rim:Value>
            urn:no:kith:xmlstds:epikrise:2006-09-23
        </rim:Value> 
    </rim:ValueList> 
</rim:Slot>

Response

In FindDocuments stored queries, a Document Consumer can choose between two response types:

1. ObjectRef: Returns only the documents' unique identificators (UUID and homeCommunityID)
2. LeafClass: Returns all metadata the system can return.

When the response type "LeafClass" is used in an ITI-18 FindDocument or GetDocuments stored query, the Document Register shall always return at least all required metadata as described in the Norwegian IHE XDS metadata profile. An example response is included in chapter 5.

ITI-43 Retrieve document set

ITI-43 is used by Document Consumer and XCA gateway to retrieve one or a set of documents from Document Repository.

ITI-43 Request

The Document Consumer must use the following attributes received from Document Registry via ITI-18 Registry Stored Query:

1. DocumentEntry ID: documentUniqueId,
2. Document Repository ID: repositoryUniqueId and
3. Affinity domain ID: homeCommunityID

<RetrieveDocumentSetRequest xmlns="urn:ihe:iti:xds-b:2007">
    <DocumentRequest>
        <HomeCommunityId>urn:oid:2.16.578.1.34.1.62.6.2</HomeCommunityId>
        <RepositoryUniqueId>2.16.578.1.34.1.20.6.2</RepositoryUniqueId>
        <DocumentUniqueId>urn:uuid:17ff9ea5-0000-0000-0000-000000000000</DocumentUniqueId>
    </DocumentRequest>
</RetrieveDocumentSetRequest>

Search parameters for stored query GetDocuments

Retrieve a collection of XDSDocumentEntry objects. XDSDocumentEntry objects are selected either by their entryUUID or uniqueId attribute. See Table 9 for description of parameters.

ITI-43 Response

The Response must be a Retrieve Document Set Response message. In this message a RegistryResponse must be included which contain a status of type ResponseStatusType that provides the overall status of the request. For each document the response message must return:

1. documentUniqueId,
2. repositoryUniqueId
3. homeCommunityID
4. mimeType
5. The retrieved document as a XOP Infoset
6. Errors or warnings in case the document(s) could not be retrieved successfully

ITI-38 Cross Gateway Query

The scope of the Cross Gateway Query transaction is based on the Registry Stored Query [ITI18] transaction. The same set of stored queries is required to be supported in both of these transactions, namely FindDocuments and GetDocuments (see description on ITI-18). The Cross Gateway Query is always between an Initiating Gateway and Responding Gateway. National usage of ITI-38 will not support the following:

• Stored queries that rely on concepts that a community may not support, namely associations, folders and submission sets. A Responding Gateway can respond with zero entries for such stored queries.
• the Asynchronous Web Services Exchange Option.

ITI TF-2b chapter 3.38.1 states that there shall be an agreed upon common coding/vocabulary scheme used for the Cross Gateway Query to prevent any need of transformation between an Initiating Gateway and a Responding Gateway. As common coding/vocabulary scheme the Norwegian XDS metadata profile shall be used. Each actor who sends or receives an ITI-38 must therefore be compliant with the Norwegian XDS metadata profile.

An Initiating Gateway shall ensure that:

• Each "getDocuments" stored query must include a homeCommunityID.
• A received "getDocuments" request including multiple documents only includes one homeCommunityID.
• Each Cross Gateway Query request includes at most one homeCommunityID.

Each community must have a unique homeCommunityID. An Initiating Gateway must administrate a directory of all communities. The directory must include for each community at least one homeCommunityIDs and the corresponding Responding Gateway(s) which serves the community. An Initiating Gateway must support that a Responding Gateway can serve multiple communities (multiple homeCommunityIDs) and that a Community can have multiple Responding Gateways.

XDS Affinity Domain Option is required for all Initiating Gateways

An Initiating Gateway must support the XDS Affinity Domain Option which means that the gateway must support receiving ITI-18 requests.
When an Initiating Gateway with the XDS Affinity Domain Option enabled receives an ITI-18 FindDocuments stored query, it shall generate and send an ITI-38 Cross Gateway Query to each registered community. Each response shall be aggregated in an ITI-18 response. All successes and failures received from different Responding Gateways shall be reflected in the response.

Grouping of actors

IHE ITI-1 chapter 18.2.3 describes permitted groupings of actors. When an Initiating Gateway is supporting an XDS Affinity Domain, it can choose to query (with ITI-18) and retrieve (with ITI-43) from local actors in addition to remote communities. This is accomplished by grouping the Initiating Gateway with a Document Consumer Actor. This grouping allows Document Consumers such as EHR/PHR/etc. systems to query the Initiating Gateway to retrieve document information and content from both the local XDS Affinity Domain as well as remote communities.

ITI-39 Cross Gateway Retrieve

The scope of the Cross Gateway Retrieve transaction is semantically the same as the Retrieve Document Set [ITI-43] transaction. The Cross Gateway Retrieve is always just between an Initiating Gateway and a Responding Gateway. In Norway it is not a requirement to support the Asynchronous Web Services Exchange Option which is normally a mandatory option for Responding Gateways.

XDS Affinity Domain Option is required for an Initiating Gateway

An Initiating Gateway must support the XDS Affinity Domain Option which means that the gateway must support receiving ITI-43 requests. The IHE profile specifies that an ITI-43 request can include request for multiple documents which resides in different communities. An Initiating Gateway must therefore support to send an ITI-39 transaction to each community and aggregate the received results in an ITI-43 response.

Section 5: Norwegian profile for XDS metadata

This section provides a description of the metadata for the Norwegian XDS profile. This applies both to which attributes to use, how the attributes are to be used and which coding systems are to be used.
XDS is content-agnostic, meaning it has no knowledge of the content of the document being shared or made available in an XDS solution. Whether the document is a PDF, an XML file or an image makes no difference to the XDS solution, it will in any case just treat the file as a document without regard to content or format. Since XDS solutions have no relation to the content of the document, metadata must be registered that describe, among other things, the overall clinical content of the documents. It is this metadata that is used when searching for specific documents. The metadata are divided into the following areas:

• Patient Identity: Attribute that identifies the patient that a document deals with, including patient ID (national identity number) and name.
• Source/Provenance: Attribute that describes where the document has been generated.
• Security & Privacy: Attribute that describes security rules and can be used to control access to the document.
• Description of Content (Descriptive): Attribute that describes the clinical content of the document. This is an attribute that is important for performing searches and finding documents based on clinical "search parameters".
• Document Status (Object Lifecycle): Attribute that describes the status of the document and any relationships to other documents Exchange: Attribute that describes how the document can be exchanged ("pull" or "push")

Use of XDS and information security

This profile does not describe how different users and solutions should access documents that are made available for lookup in an XDS solution. XDS has several metadata attributes, such as the company (authorInstitution) that produced the document and the type of document (classCode/typeCode), which can provide a basis for how security and access management can be ensured. However, there is no "built-in" security/access control in the metadata attributes directly, this must be taken care of by the solutions that together constitute one or more XDS areas and via the system solutions that provide access to documents in an XDS solution

Profile description

SubmissionSet

SubmissionSet means that one submits multiple documents in a "package" and the metadata for the SubmissionSet can be compared to the package label on a package. This metadata summarizes the contents of the SubmissionSet and how documents, relationships, and folders are placed together. An example of when a SubmissionSet can be used is when one wants to collect all documents related to a hospital stay for a patient. When submitting a SubmissionSet it is the case that either all of the documents are put in the document archive. That is, if there is an error related to one of the documents, none of the documents will be placed in the archive.

DocumentEntry

In this context, a DocumentEntry is the metadata registered on the individual document that is to be made available and shared in an XDS solution. This metadata does not contain the content of the document itself, but only metadata about the document. There are two types of DocumentEntry:

• Stable DocumentEntry
• On-demand DocumentEntry

A "Stable DocumentEntry" contains data about a document that has already been generated and exists, and is available for download via the XDS solution.
An "On-demand DocumentEntry" contains metadata with a unique id that can be used to generate a document when a request has been made for the document with that id.
In this way, one can access a document that contains the latest relevant information that the document is intended to contain. XDS areas that need to use "on-demand entry" may have to describe how such use of XDS should take place.

Folder

A Folder is a logical collection of those documents that have a relationship to each other. A Folder can be updated by multiple SubmissionSets, also sent from several different companies. This may, for example, be to collect all documents belonging to a laboratory examination, both the laboratory requisition and the associated laboratory results. This document does not specifically describe how to use Folder.

Overview of XDS attributes

XDS metadata in Norwegian profile

The following tags are used to indicate whether a metadata attribute is required or optional:

A system integrated with an XDS solution must be able to receive and manage all attributes specified by tags R, R2, or O.

For some attributes, the content to be recorded for the various metadata attributes can be retrieved from different data sources. For example, the data sources can be an discharge summary document that contains information that can be included in one or more metadata attributes. Which data sources may be relevant for different metadata attributes may vary between different solutions/professional systems used.
The table below shows possible data sources for the metadata information.

¹ This attribute shall not be used for "on-demand" type documents.
² This attribute is not part of the profile, but can be tried out.
³ This attribute shall not be used for "on-demand" type documents.

Datatypes

The datatypes used are according to the XDS specification from IHE.

OIDs

The table below gives an overview of which OIDs (Object-identifiers) are used in the metadata profile. |Kategori|OID| |---|---| |Kodeverk på Volven.no|2.16.578.1.12.4.1.1.XXXX| |Fødselsnummer|2.16.578.1.12.4.1.4.1| |D-nummer|2.16.578.1.12.4.1.4.2| |Felles|hjelpenummer|2.16.578.1.12.4.1.4.3| |HPR-nummer|2.16.578.1.12.4.1.4.4| |Duf-nummer|2.16.578.1.12.4.1.4.5| |Organisasjonsnummer|2.16.578.1.12.4.1.4.101|

UUIDs in use in metadata

Submission Set

DocumentEntry object

XDS attributes in Norwegian profile

Author

The following classificationScheme shall be used for DocumentEntry and SubmissionSet, respectively:

• DocumentEntry.author: urn:uuid:93606bcf-9494-43ec-9b4e-a7748d1a838d
• SubmissionSet.author: urn:uuid:a7058bb9-b4e4-4307-ba5b-e3f0ab85e12d

AuthorInstitution

<rim:Slot name="authorInstitution">
    <rim:ValueList>
        <rim:Value>
        St Olavs Hospital HF^^^^^&2.16.578.1.12.4.1.4.101&ISO^^^^8883974832
        </rim:Value>
    </rim:ValueList>
</rim:Slot>

<rim:Slot name="authorInstitution">
    <rim:ValueList>
        <rim:Value>Medisinsk klinikk^^^^^&2.16.578.1.12.4.1.4.102&ISO^^^^104218</rim:Value>
        <rim:Value>St Olavs Hospital HF^^^^^&2.16.578.1.12.4.1.4.101&ISO^^^^883974832</rim:Value>
    </rim:ValueList>
</rim:Slot>

AuthorPerson

<rim:Slot name="authorPerson">
    <rim:ValueList>
        <rim:Value>9144889^Koman^Magnar^^^^^^& 2.16.578.1.12.4.1.4.4&ISO</rim:Value>
    </rim:ValueList>
</rim:Slot>

AuthorRole

<rim:Slot name="authorRole">
    <rim:ValueList>
        <rim:Value>10^^^&2.16.578.1.12.4.1.1.9034&ISO </rim:Value>
    </rim:ValueList>
</rim:Slot>

AuthorSpeciality

<rim:Slot name="authorSpeciality">
    <rim:ValueList>
        <rim:Value>35^^^&2.16.578.1.12.4.1.1.7426&ISO </rim:Value>
    </rim:ValueList>
</rim:Slot>

availabilityStatus

<ExtrinsicObject
    id="urn:uuid:fbeacdb7-5421-4474-9267-985007cd8855"
    objectType="urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1"
    status="urn:oasis:names:tc:ebxml-regrep:StatusType:Approved">

classCode

<rim:Classification 
    classificationScheme="urn:uuid:41a5887f-8865-4c09-adf7-e362475b143a" 
    classifiedObject="ExampleDocument" 
    id="IdExample_046" 
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:Classification" 
    nodeRepresentation=" A00-1">
    <rim:Name>
        <rim:LocalizedString value="Epikriser og sammenfatninger"/>
    </rim:Name>
    <rim:Slot name="codingScheme">
        <rim:ValueList>
            <rim:Value>2.16.578.1.12.4.1.1.9602</rim:Value>
        </rim:ValueList>
    </rim:Slot>
</rim:Classification>

comments

The comments attribute is not used in this profile.

confidentialityCode

<rim:Classification 
    classificationScheme="urn:uuid:f4f85eac-e6cb-4883-b524-f2705394840f"
    classifiedObject="ExampleDocument"
    id="IdExample_046"
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:Classification"
    nodeRepresentation="N">
    <rim:Name>
        <rim:LocalizedString value="Normal"/>
    </rim:Name>
    <rim:Slot name="codingScheme">
        <rim:ValueList>
            <rim:Value>2.16.578.1.12.4.1.1.9603</rim:Value>
        </rim:ValueList>
    </rim:Slot>
</rim:Classification>

contentTypeCode

The contentTypeCode attribute is not used in this profile

creationTime

<rim:Slot name="creationTime"> 
    <rim:ValueList> 
        <rim:Value>20150825153720</rim:Value> 
    </rim:ValueList> 
</rim:Slot> 

entryUUID

<rim:ExtrinsicObject mimeType="text/xml" 
    id="urn:uuid:a6e06ca8-0c75-4064-9e5c-88b9045a96f6" 
    objectType="urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1"  
</rim:ExtrinsicObject> 

eventCodeList

<rim:Classification 
    classificationScheme="urn:uuid:2c6b8cb7-8b2a-4051-b291-b1ae6a575ef4" 
    classifiedObject="ExampleDocument" 
    id="IdExample_048" 
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:Classification" 
    nodeRepresentation="AAA27">
    <rim:Name>
        <rim:LocalizedString value="Innlegging av intracerebral trykkmåler"/>
    </rim:Name>
    <rim:Slot name="codingScheme">
        <rim:ValueList>
            <rim:Value>2.16.578.1.12.4.1.1.7210</rim:Value>
        </rim:ValueList>
    </rim:Slot>
</rim:Classification>

formatCode

<rim:Classification 
    classificationScheme="urn:uuid:a09d5840-386c-46f2-b5ad-9c3699a4309d" 
    classifiedObject="ExampleDocument" 
    id="IdExample_049" 
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:Classification"
    nodeRepresentation="ExampleformatCode">
    <rim:Name>
        <rim:LocalizedString value="Resept"/>
    </rim:Name>
    <rim:Slot name="codingScheme">
        <rim:ValueList>
            <rim:Value>urn:no:kith:xmlstds:eresept:m1:2013-1008</rim:Value>
        </rim:ValueList>
    </rim:Slot>
</rim:Classification>

hash

<rim:Slot name="hash"> 
    <rim:ValueList>     
        <rim:Value>da39a3ee5e6b4b0d3255bfef95601890afd80709</rim:Value> 
    </rim:ValueList> 
</rim:Slot> 

healthcareFacilityTypeCode

<rim:Classification     
    classificationScheme="urn:uuid:f33fb8ac-18af-42cc-ae0e-ed0b0bdb91e1"
    classifiedObject="ExampleDocument"
    id="IdExample_050" 
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:Classification" 
    nodeRepresentation="86.101"> 
    <rim:Name> 
        <rim:value "Alminnelige somatiske sykehus"/> 
    </rim:Name> 
    <rim:Slot name="codingScheme"> 
        <rim:ValueList> 
            <rim:Value>2.16.578.1.12.4.1.1.1303</rim:Value> 
        </rim:ValueList> 
    </rim:Slot> 
</rim:Classification> 

homeCommunityID

<rim:ExtrinsicObject home="urn:oid:1.2.3" ...> 
...  
</rim:ExtrinsicObject> 

intendedRecipient

The attribute is Optional for those who want to try it out.

<rim:Slot name="intendedRecipient"> 
    <rim:ValueList> 
        <rim:Value>
            Et Sykehusl^^^^^^^^^1.2.3.9.1789.45|
            ^Ola^Nordmann^^^Dr^MD|
            ^^Internet^ola@l@healthcare.example.org
        </rim:Value> 
    </rim:ValueList> 
</rim:Slot> 

languageCode

<rim:Slot name="languageCode"> 
    <rim:ValueList> 
        <rim:Value>”nb-NO”</rim:Value> 
    </rim:ValueList> 
</rim:Slot> 

legalAuthenticator

<rim:Slot name="legalAuthenticator"> 
    <rim:ValueList> 
        <rim:Value>
        9144889^Koman^Magnar^^^^^^&2.16.578.1.12.4.1.4.4&ISO
        </rim:Value> 
    </rim:ValueList> 
</rim:Slot>

limitedMetadata

The limitedMetadata attribute is not used in this profile.

mimeType

<rim:ExtrinsicObject 
    mimeType="text/xml"     
    id="ExampleDocument" 
    objectType="urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1"> 
</rim:ExtrinsicObject>

objectType

<rim:ExtrinsicObject 
    mimeType="text/xml" 
    id="urn:uuid:a6e06ca8-0c75-4064-9e5c-88b9045a96f6" 
    objectType="urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1">

patientId

<rim:ExternalIdentifier 
    identificationScheme="urn:uuid:58a6f841-87b3-4a3e-92fda8ffeff98427" 
    value="15076500565^^^&2.16.578.1.12.4.1.4.1&ISO"
    id="IdExample_051"
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:ExternalIdentifier"
    registryObject="DocumentEntry01"> 
    <rim:Name> 
        <rim:LocalizedString value="XDSDocumentEntry.patientId "/> 
    </rim:Name> 
</rim:ExternalIdentifier> 

practiceSettingCode

<rim:Classification
    ClassificationScheme="urn:uuid:cccf5598-8b07-4b77-a05eae952c785ead"
    classifiedObject="ExampleDocument" 
    id="IdExample_052"
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:Classification"
    nodeRepresentation="2.16.578.1.12.4.1.1.8655">
    <rim:Name>
        <rim:LocalizedString value="Kirurgi" />
    </rim:Name>
    <rim:Slot name="codingScheme">
        <rim:ValueList>
            <rim:Value>S02 </rim:Value>
        </rim:ValueList>
    </rim:Slot>

referenceIdList

<rim:Slot name="urn:ihe:iti:xds:2013:referenceIdList">
    <rim:ValueList>
        <rim:Value>2013001^^^&1.2.3.4.5.6&ISO^urn:ihe:iti:xds:2013:accession</rim:Value>
        <rim:Value> 1.2.3.12.78.23^^^^urn:ihe:iti:xds:2013:uniqueId^&1.2.3.4&ISO</rim:Value>
    </rim:ValueList>
</rim:Slot>

repositoryUniqueId

<rim:Slot name="repositoryUniqueId"> 
    <rim:ValueList> 
        <rim:Value>1.3.6.1.4.5</rim:Value> 
    </rim:ValueList> 
</rim:Slot>

serviceStartTime

<rim:Slot name="serviceStartTime"> 
    <rim:ValueList> 
        <rim:Value>20151016212010</rim:Value> 
    </rim:ValueList> 
</rim:Slot> 

serviceStopTime

<rim:Slot name="serviceStartTime"> 
    <rim:ValueList> 
        <rim:Value>20151016223545</rim:Value> 
    </rim:ValueList> 
</rim:Slot> 

size

<rim:Slot name="size"> 
    <rim:ValueList> 
        <rim:Value>7411</rim:Value> 
    </rim:ValueList> 
</rim:Slot> 

sourcePatientId

<rim:Slot name="sourcePatientId"> 
    <rim:ValueList> 
    <rim:Value>
        15076500565^^^&2.16.578.1.12.4.1.4.1&ISO 
    </rim:Value> 
    </rim:ValueList> 
</rim:Slot>

sourcePatientInfo

<rim:Slot name="sourcePatientInfo"> 
    <rim:ValueList>
        <rim:Value>PID-5|Gundersen^Roland^Arne^^^</rim:Value>
        <rim:Value>PID-7|19650715</rim:Value>
        <rim:Value>PID-8|M</rim:Value>
    </rim:ValueList>
</rim:Slot>

submissionTime

<rim:Slot name="submissionTime"> 
    <rim:ValueList> 
        <rim:Value>20151026163000</rim:Value> 
    </rim:ValueList> 
</rim:Slot> 

title

<rim:ExtrinsicObject     
    id="ExampleDocument" 
    objectType="urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1"
    mimeType="text/xml"> 
    <rim:Name> 
        <rim:LocalizedString value="Operasjonsnotat for 15076500565"/>
    </rim:Name> 
[...] 
</rim:ExtrinsicObject> 

typeCode

<rim:Classification 
    classificationScheme="urn:uuid:f0306f51-975f-434ea61c-c59651d33983"  
    classifiedObject="EksempelEpikrise"
    nodeRepresentation=" A03-2"
    id="IdExample_053"  
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:Classification"> 
    <rim:Name> 
        <rim:LocalizedString value="Epikrise"/> 
    </rim:Name> 
    <rim:Slot name="codingScheme"> 
        <rim:ValueList> 
            <rim:Value>2.16.578.1.12.4.1.1.9602</rim:Value> 
        </rim:ValueList> 
    </rim:Slot> 
</rim:Classification>

uniqueId

<rim:ExternalIdentifier
    id="urn:uuid:e8281697-86d0-40a6-8edd-201cd360fe3b"
    objectType="urn:oasis:names:tc:ebxml-regrep:ObjectType:RegistryObject:ExternalIdentifier"
    registryObject="urn:uuid:103d9e5d-0000-0000-0000-000000000000"  
    identificationScheme="urn:uuid:2e82c1f6-a085-4c72-9da3-8640a32e42ab"  
    value="^272473693">
    <rim:Name>
        <rim:LocalizedString value="XDSDocumentEntry.uniqueId"/>  	
    </rim:Name> 
</rim:ExternalIdentifier>

URI

<rim:Slot name="URI"> 
    <rim:ValueList> 
        <rim:Value>DOC001.XML</rim:Value> 
    </rim:ValueList> 
</rim:Slot>