Sharing of IPS (sIPS)
1.0.1-current - ci-build International flag

Sharing of IPS (sIPS), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 1.0.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.sIPS/ and changes regularly. See the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

IHE sIPS Content Consumer Actor

CapabilityStatement for the IHE sIPS Content Consumer Actor

The Content Consumer consumes the IPS content and obtains it using one of the methods defined in the IHE Document Sharing Health Information Exchange.

FHIR Capability Statement for [Content Consumer]{CapabilityStatement-IHE.sIPS.ContentConsumer.html}

The HL7 IPS is mapped to the Document Sharing Metadata according to PCC Volume 2: 4.1. This shows how to map the FHIR Composition resource elements into XDS/XDM/XDR/XCA Document Entry and MHD FHIR DocumentReference elements.
IHE sIPS Content Creator Actor

CapabilityStatement for the IHE sIPS Content Creator Actor

The Content Creator creates the IPS content and shares it using one of the methods defined in the IHE Document Sharing Health Information Exchange.

FHIR Capability Statement for [Content Creator]{CapabilityStatement-IHE.sIPS.ContentCreator.html}

The HL7 IPS is mapped to the Document Sharing Metadata according to PCC Volume 2: 4.1. This shows how to map the FHIR Composition resource elements into XDS/XDM/XDR/XCA Document Entry and MHD FHIR DocumentReference elements.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

DocumentReference for the Bundle-01 IPS document in JSON

Example of a Comprehensive DocumentReference resource.

  • This is for the JSON encoding. Links in Transform relationship to the XML encoded form.
  • Where the IPS Bundle is the IPS examples 01
  • This is fully filled for all mandatory elements.
  • IPS has multiple authenticators, XDS DocumentEntry has only one available
  • IPS does not have a class, Comprehensive requires a category - replicated the type.
  • IPS didn’t have a declared language, presumed US
  • made up an inline Patient
  • facility and practice setting come from publisher policy or setting and are not derived from Composition
DocumentReference for the Bundle-01 IPS document in XML

Example of a Comprehensive DocumentReference resource.

  • This is for the XML encoding
  • Where the IPS Bundle is the IPS examples 01
  • This is fully filled for all mandatory elements.
  • IPS has multiple authenticators, XDS DocumentEntry has only one available
  • IPS does not have a class, Comprehensive requires a category - replicated the type.
  • IPS didn’t have a declared language, presumed US
  • made up an inline Patient
  • facility and practice setting come from publisher policy or setting and are not derived from Composition
HIE Managed instance of Organization for Anorg Aniza

Example of mCSD managed Organization
HIE managed instance of Patient for Martha DeLarosa

Example of an PDQm managed Patient
HIE managed instance of Practitioner for Beetje van Hulp

Example of mCSD managed Practitioner