Unattributed Code Systems

Copyright and Registered Trademark Uses

External References

Type Reference Content
web tel:+31-51-34343400 telecom : +31-51-34343400
web tel:+31788700800 +31788700800
web tel:+33-555-20036 +33-555-20036
web profiles.ihe.net
web profiles.ihe.net
web github.com 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
web www.ihe.net IG © 2023+ IHE IT Infrastructure Technical Committee . Package ihe.iti.sips#1.0.1-current based on FHIR 4.0.1 . Generated 2025-02-27
Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web github.com Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web github.com Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web profiles.ihe.net Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web www.ihe.net Links: Table of Contents | QA Report | New Issue | Issues Version History | CC0 | Propose a changeexternal
web profiles.ihe.net The Content Consumer consumes the IPS content and obtains it using one of the methods defined in the IHE Document Sharing Health Information Exchange .
web profiles.ihe.net 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.
web profiles.ihe.net The Content Creator creates the IPS content and shares it using one of the methods defined in the IHE Document Sharing Health Information Exchange .
web profiles.ihe.net Editor, add the following new section to ITI Volume 3 :
web profiles.ihe.net The IHE sIPS does not modify the HL7 IPS specification, but provides for methods of sharing the IPS using IHE Document Sharing . The IPS, as a “current summary”, is an excellent document for the “On-Demand” capability of the Document Sharing infrastructure. On-Demand is available in XDS with On-Demand Documents Option , XCA with On-Demand Documents Option , and with MHD/MHDS . Further details for IPS use of On-Demand are outlined below in section 3.9.2.1.2.
web profiles.ihe.net The IHE sIPS does not modify the HL7 IPS specification, but provides for methods of sharing the IPS using IHE Document Sharing . The IPS, as a “current summary”, is an excellent document for the “On-Demand” capability of the Document Sharing infrastructure. On-Demand is available in XDS with On-Demand Documents Option , XCA with On-Demand Documents Option , and with MHD/MHDS . Further details for IPS use of On-Demand are outlined below in section 3.9.2.1.2.
web profiles.ihe.net The IHE sIPS does not modify the HL7 IPS specification, but provides for methods of sharing the IPS using IHE Document Sharing . The IPS, as a “current summary”, is an excellent document for the “On-Demand” capability of the Document Sharing infrastructure. On-Demand is available in XDS with On-Demand Documents Option , XCA with On-Demand Documents Option , and with MHD/MHDS . Further details for IPS use of On-Demand are outlined below in section 3.9.2.1.2.
web profiles.ihe.net The IHE sIPS does not modify the HL7 IPS specification, but provides for methods of sharing the IPS using IHE Document Sharing . The IPS, as a “current summary”, is an excellent document for the “On-Demand” capability of the Document Sharing infrastructure. On-Demand is available in XDS with On-Demand Documents Option , XCA with On-Demand Documents Option , and with MHD/MHDS . Further details for IPS use of On-Demand are outlined below in section 3.9.2.1.2.
web profiles.ihe.net The IHE sIPS does not modify the HL7 IPS specification, but provides for methods of sharing the IPS using IHE Document Sharing . The IPS, as a “current summary”, is an excellent document for the “On-Demand” capability of the Document Sharing infrastructure. On-Demand is available in XDS with On-Demand Documents Option , XCA with On-Demand Documents Option , and with MHD/MHDS . Further details for IPS use of On-Demand are outlined below in section 3.9.2.1.2.
web profiles.ihe.net The IHE sIPS does not modify the HL7 IPS specification, but provides for methods of sharing the IPS using IHE Document Sharing . The IPS, as a “current summary”, is an excellent document for the “On-Demand” capability of the Document Sharing infrastructure. On-Demand is available in XDS with On-Demand Documents Option , XCA with On-Demand Documents Option , and with MHD/MHDS . Further details for IPS use of On-Demand are outlined below in section 3.9.2.1.2.
web profiles.ihe.net The IHE Document Sharing infrastructures define a common set of Document Metadata, Submission Set, and Folders. There are defined methods of communicating documents including push, centralized registry, and federated discovery and retrieval. The metadata model is designed to be content agnostic so it can support any past or future document specification, which enables all existing networks to support the IPS without modification.
web profiles.ihe.net The IHE Document Sharing infrastructures define a common set of Document Metadata, Submission Set, and Folders. There are defined methods of communicating documents including push, centralized registry, and federated discovery and retrieval. The metadata model is designed to be content agnostic so it can support any past or future document specification, which enables all existing networks to support the IPS without modification.
web profiles.ihe.net A Document Entry (aka FHIR DocumentReference) is metadata about a document. This metadata is designed to support provenance, lifecycle, authenticity, patient identity, privacy, and exchange of the document that is described. The document can be any kind of format, in this content module we are focused on the International Patient Summary (IPS) document and the format of JSON or XML. Submission Set is the metadata about the publication event, who published these documents, why, when, where, etc. The Folder is an adhoc grouping mechanism that can be used for purposes like grouping a clinical episode. Further explanation of the Value of Metadata is covered in the HIE Whitepaper .
web profiles.ihe.net A Document Entry (aka FHIR DocumentReference) is metadata about a document. This metadata is designed to support provenance, lifecycle, authenticity, patient identity, privacy, and exchange of the document that is described. The document can be any kind of format, in this content module we are focused on the International Patient Summary (IPS) document and the format of JSON or XML. Submission Set is the metadata about the publication event, who published these documents, why, when, where, etc. The Folder is an adhoc grouping mechanism that can be used for purposes like grouping a clinical episode. Further explanation of the Value of Metadata is covered in the HIE Whitepaper .
web profiles.ihe.net There is a limitation in the Document Sharing metadata that each Document entry must have only one mime-type. The FHIR model supports many mime-type encodings, as does IPS. Some environments may choose one of the FHIR mime-type encodings, where others may need both JSON and XML mime-type encoding of the IPS document bundle. Where more than one mime-type encoding is needed, one would need to register multiple Document entries and indicate they are transforms only differing in mime-type. With multiple Document entries registered, the Document Consumer can pick the mime-type desired, and with the transform relationship be confident that there is no semantic difference between the two mime-type encodings.
web profiles.ihe.net When the Document Source is willing to offer to Document Consumers the ability for an on on-demand instance of the IPS to be returned using current data, it can register a Document Entry (DocumentReference) as “On-Demand” . XDS and XCA the On-Demand entry is indicated with a given On-Demand ObjectType as expressed in the given options, in MHD/MHDS an On-Demand entry is indicated with an absent .size and .hash. The Document Entry (DocumentReference) will express specific parameters that would be used if the Document Consumer were to request a document be created “On-Demand”; such as timeperiod refinements, setting, language, etc.
web profiles.ihe.net The returned document would, based on configuration, result in an additional DocumentEntry/DocumentReference (aka Snapshot) existing that is in snapshot relationship with the On-Demand DocumentEntry/DocumentReference, and representing the returned document metadata. This snapshot is a “stable” instance that can be retrieved again in the future. More discussion of the relationship between the on-demand and the instances that are preserved as snapshots is explain in HIE Whitepaper: Dynamic Documents .
web github.com The source code for this Implementation Guide can be found on IHE ITI.sIPS Github Repo .
web profiles.ihe.net Sharing of IPS (sIPS) - defines how HL7 FHIR IPS is communicated using IHE Document Sharing Health Information Exchange .
web profiles.ihe.net IHE uses the normative words: Shall, Should, and May according to standards conventions .
web www.ihe.net The PCC-IPS is being broken up into distinct profiles starting with the sIPS Implementation Guide (Profile). Other parts of PCC-IPS are expected to be published in the coming months and years as resources become available. The sIPS takes precedence over equivalent profiling found in the PCC-IPS ; however, those parts of the PCC-IPS that have not been published in other forms are still relevant.
web github.com IHE welcomes New Issues from the GitHub community. For those without GitHub access, issues may be submitted to the ITI Public Comment form .
web www.ihe.net IHE welcomes New Issues from the GitHub community. For those without GitHub access, issues may be submitted to the ITI Public Comment form .
web github.com As issues are submitted they will be managed on the sIPS GitHub Issues , where discussion and workarounds may be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later).
web wiki.ihe.net As issues are submitted they will be managed on the sIPS GitHub Issues , where discussion and workarounds may be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later).
web www.ihe.net As issues are submitted they will be managed on the sIPS GitHub Issues , where discussion and workarounds may be found. These issues, when critical, will be processed using the normal IHE Change Proposal management and balloting. It is important to note that as soon as a Change Proposal is approved, it carries the same weight as a published Implementation Guide (i.e., it is testable at an IHE Connectathon from the time it is approved, even if it will not be integrated until several months later).
web github.com sIPS_001: Minimal View Option is referring the reader to FHIR Core for Documents. Are there more specific requirements available from IPS or IHE?
web profiles.ihe.net Editor, add the following new or modified actors to the IHE Technical Frameworks General Introduction Appendix A :
web profiles.ihe.net Editor, add the following new or modified transactions to the IHE Technical Frameworks General Introduction Appendix B :
web profiles.ihe.net Editor, add the following new or modified terms to the IHE Technical Frameworks General Introduction Appendix D :
web www.ihe.net The following is an excerpt from PCC Volume 2 : It is provided here for convenience to the reader and is not intended to be different. It does have CP-PCC-0300 integrated.
web profiles.ihe.net Cross Enterprise Document Sharing (XDS)
web profiles.ihe.net Cross Enterprise Document Sharing on Media (XDM)
web profiles.ihe.net Cross Enterprise Document Sharing Reliable Ex (XDR)
web profiles.ihe.net Cross Community Access (XCA)
web profiles.ihe.net Multi-Patient Query (MPQ)
web profiles.ihe.net ​ Mobile Health Document Sharing (MHDS)
web profiles.ihe.net The source for all required and optional attributes have been defined in the bindings below. Two tables describe the XDS object types: XDSDocumentEntry, and XDSSubmissionSet. The definitions of the metadata attributes is defined in ITI Volume 3:4 , with the optionality defined in ITI Volume 3:4.3 . For a mapping between DocumentReferenece and XDS DocumentEntry attributes see http://hl7.org/fhir/documentreference-mappings.html#xds .
web profiles.ihe.net The source for all required and optional attributes have been defined in the bindings below. Two tables describe the XDS object types: XDSDocumentEntry, and XDSSubmissionSet. The definitions of the metadata attributes is defined in ITI Volume 3:4 , with the optionality defined in ITI Volume 3:4.3 . For a mapping between DocumentReferenece and XDS DocumentEntry attributes see http://hl7.org/fhir/documentreference-mappings.html#xds .
web profiles.ihe.net This binding defines a transformation that generates metadata for the XDSDocumentEntry and XDSSubmissionSet elements of appropriate transactions from the Document Sharing profiles given a medical document and information from other sources. The medical document refers to the document being stored in a repository that will be referenced in the registry. The other sources of information include the configuration of the Document Source Actor, the XDS Affinity Domain, the site or facility, local agreements, other documents in the registry/repository, and this Content Profile. See Overview of Health Document Sharing Communities .
web profiles.ihe.net This binding defines a transformation that generates metadata for the XDSDocumentEntry and XDSSubmissionSet elements of appropriate transactions from the Document Sharing profiles given a medical document and information from other sources. The medical document refers to the document being stored in a repository that will be referenced in the registry. The other sources of information include the configuration of the Document Source Actor, the XDS Affinity Domain, the site or facility, local agreements, other documents in the registry/repository, and this Content Profile. See Overview of Health Document Sharing Communities .
web profiles.ihe.net This binding defines a transformation that generates metadata for the XDSDocumentEntry and XDSSubmissionSet elements of appropriate transactions from the Document Sharing profiles given a medical document and information from other sources. The medical document refers to the document being stored in a repository that will be referenced in the registry. The other sources of information include the configuration of the Document Source Actor, the XDS Affinity Domain, the site or facility, local agreements, other documents in the registry/repository, and this Content Profile. See Overview of Health Document Sharing Communities .
web profiles.ihe.net In many cases, the CDA/FHIR document is created for the purposes of sharing within an XDS Affinity Domain. In these cases the context of the CDA/FHIR Document and the context of the XDS Affinity Domain are the same, in which case the following mappings shall apply.
web profiles.ihe.net In other cases, the CDA/FHIR document may have been created for internal use, and are subsequently being shared. In these cases the context of the CDA/FHIR document would not necessarily coincide with that of the XDS Affinity Domain, and the mappings below would not necessarily apply. See Principles of IHE for Health Document sharing .
web profiles.ihe.net In other cases, the CDA/FHIR document may have been created for internal use, and are subsequently being shared. In these cases the context of the CDA/FHIR document would not necessarily coincide with that of the XDS Affinity Domain, and the mappings below would not necessarily apply. See Principles of IHE for Health Document sharing .
web profiles.ihe.net The Sharing of IPS (sIPS) IHE Profile provides for methods of exchanging the HL7 International Patient Summary (IPS) , using IHE Document Sharing Health Information Exchange but does not modify the HL7 IPS specification. The International Patient Summary (IPS) content, as defined in the ISO 27269 data model specification, utilizes IHE’s document sharing infrastructure including cross-community, HIE, direct exchange models, and more. It has been designed specifically to remove barriers to adoption, by leveraging architectures that are currently implemented, well-established, and robust. The sIPS Profile provides implementation guidance to vendors and implementers and joins a growing suite of IPS standards artifacts contributed by a variety of Standards Development Organizations (SDOs) and coordinated by the Joint Initiative Council for Global Health Informatics Standardization (JIC) .
web www.iso.org The Sharing of IPS (sIPS) IHE Profile provides for methods of exchanging the HL7 International Patient Summary (IPS) , using IHE Document Sharing Health Information Exchange but does not modify the HL7 IPS specification. The International Patient Summary (IPS) content, as defined in the ISO 27269 data model specification, utilizes IHE’s document sharing infrastructure including cross-community, HIE, direct exchange models, and more. It has been designed specifically to remove barriers to adoption, by leveraging architectures that are currently implemented, well-established, and robust. The sIPS Profile provides implementation guidance to vendors and implementers and joins a growing suite of IPS standards artifacts contributed by a variety of Standards Development Organizations (SDOs) and coordinated by the Joint Initiative Council for Global Health Informatics Standardization (JIC) .
web international-patient-summary.net The Sharing of IPS (sIPS) IHE Profile provides for methods of exchanging the HL7 International Patient Summary (IPS) , using IHE Document Sharing Health Information Exchange but does not modify the HL7 IPS specification. The International Patient Summary (IPS) content, as defined in the ISO 27269 data model specification, utilizes IHE’s document sharing infrastructure including cross-community, HIE, direct exchange models, and more. It has been designed specifically to remove barriers to adoption, by leveraging architectures that are currently implemented, well-established, and robust. The sIPS Profile provides implementation guidance to vendors and implementers and joins a growing suite of IPS standards artifacts contributed by a variety of Standards Development Organizations (SDOs) and coordinated by the Joint Initiative Council for Global Health Informatics Standardization (JIC) .
web jointinitiativecouncil.org The Sharing of IPS (sIPS) IHE Profile provides for methods of exchanging the HL7 International Patient Summary (IPS) , using IHE Document Sharing Health Information Exchange but does not modify the HL7 IPS specification. The International Patient Summary (IPS) content, as defined in the ISO 27269 data model specification, utilizes IHE’s document sharing infrastructure including cross-community, HIE, direct exchange models, and more. It has been designed specifically to remove barriers to adoption, by leveraging architectures that are currently implemented, well-established, and robust. The sIPS Profile provides implementation guidance to vendors and implementers and joins a growing suite of IPS standards artifacts contributed by a variety of Standards Development Organizations (SDOs) and coordinated by the Joint Initiative Council for Global Health Informatics Standardization (JIC) .
web profiles.ihe.net The IPS, as a current medical summary, is an excellent document for the “On-Demand” capability of the Document Sharing infrastructure. Further details for IPS use of On-Demand are outlined below . IHE Document Sharing also has “Stable” and “Delayed Assembly” document entry types that are further explained in the HIE Whitepaper: Dynamic Documents .
web profiles.ihe.net The HL7 IPS is serialized into a FHIR Document Bundle and encoded as a document following the PCC Serializing FHIR Documents . 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.
web profiles.ihe.net The Content Creator and Content Consumer share the IPS content using one of the methods defined in the IHE Document Sharing Health Information Exchange .
web profiles.ihe.net The Content Creator and Content Consumer communicate the content using the IHE Document Sharing Health Information Exchange .
web profiles.ihe.net Document Sharing Health Information Exchange Whitepaper includes additional HIE functionalities that are covered in the following sections:
web profiles.ihe.net Document Sharing: Profiles
web profiles.ihe.net Consuming data as FHIR Resources: Profiles, and Content
web profiles.ihe.net Patient identity Management: Whitepaper, and Profiles
web profiles.ihe.net Provider Directory Solutions: Profiles, and Content
web profiles.ihe.net Security and Privacy Solutions: Handbooks, Profiles, and Content
web profiles.ihe.net This Implementation Guide simply hooks HL7 IPS to IHE Document Sharing (XDS, XCA, XDR, XDM, MHD, MHDS) , using existing Content Creator / Content Consumer actors that already support this binding.
web profiles.ihe.net The Concepts of Document Sharing Health Information Exchange are defined in the IHE Whitepaper , and ITI Profiles .
web profiles.ihe.net The Concepts of Document Sharing Health Information Exchange are defined in the IHE Whitepaper , and ITI Profiles .
web profiles.ihe.net The IHE Document Sharing infrastructures define a common set of Document Metadata, Submission Set, and Folders. There are defined methods of communicating documents including push, centralized registry, and federated discovery and retrieval. The metadata model is designed to be content agnostic so can support any past or future document specification, which enables all existing networks to support the IPS without modification.
web profiles.ihe.net The IHE Document Sharing infrastructures define a common set of Document Metadata, Submission Set, and Folders. There are defined methods of communicating documents including push, centralized registry, and federated discovery and retrieval. The metadata model is designed to be content agnostic so can support any past or future document specification, which enables all existing networks to support the IPS without modification.
web cucumber.io Note: the above use-case is written in Gherkin , a use-case language optimized for automated testing.
web profiles.ihe.net General explanation of Centralized Discovery and Retrieve in the HIE Whitepaper
web profiles.ihe.net General explanation of Federated Discover and Retrieve in the HIE Whitepaper
web profiles.ihe.net General explanation of Document Publishing in the HIE Whitepaper
web profiles.ihe.net General explanation of Dynamic Documents in the HIE Whitepaper
web profiles.ihe.net General explanation of Document Discovery and retrieval in the HIE Whitepaper
web profiles.ihe.net General explanation of PUSH model of Document Sharing in the HIE Whitepaper
web profiles.ihe.net See Security and Privacy Solutions: Handbooks, Profiles, and Content .

Internal Images

IPS_doc_library.png
IPS_doc_library.png