iCure. eHealth Solutions
  • Developer Documentation
  • iCure Software Modules
  • Get Started
    • Create your own Database
      • Receive an invitation
      • Create new User
      • Create a new Healthcare Party
    • Structure your Database
    • Access your database
    • Use the Console
  • Data Stack Module
    • The Data Stack
      • Install iCure
      • Get Started with a Database
    • iCure Data Model
      • Overview
      • User
        • Permission
      • Healthcare Party
      • Patient
        • Insurability
        • Relationship
        • Patient Hcp care period
          • Referral period
      • Contact
        • Service
          • Content
            • Medication
              • Regimen item
            • Measure
        • SubContact
      • Healthcare Element
        • Care team member
        • Healthcare approach
      • Form
      • Additional Classes
        • AccessLog
        • Address
          • Telecom
        • Message
        • Document
        • FilterChain
          • Filter
          • Predicate
        • Group
        • Insurance
        • Invoice
          • Invoicing code
        • Tarification
          • Valorisation
    • Hybrid Cloud Storage
    • Mobile/Web SDKs
      • JavaScript/Typescript
        • Setting up your environment
        • Logging in
        • Managing patients
        • iCure for MedTech: Getting Started
          • Exchange data using FHIR model
          • Exchange data using iCure SDK
      • Java/Kotlin
      • Swift/Objective C
    • REST API calls
      • User
      • Patient
      • HealthcareParty
      • Contact
      • HealthcareElement
      • Form
      • Document
      • Message
      • Invoice
      • Additional endpoints
        • AccessLog
        • Authentication
        • Codification
        • Document template
        • Entity reference
        • Entity template
        • Insurance
        • Receipt
        • Tarification
    • Access Rights management
    • End-to-End-Encryption
    • ATNA Audit Records
  • Interoperability Module
    • IHE XDS calls
      • The XDS Concept
      • ITI-18 get associations api call
      • ITI-41 provide and register document set api call
      • Iti-42 register document set api call
    • IHE IPS call
      • The IPS Concept
    • FHIR API Data Exchange
      • The FHIR Concept
    • Freehealth Connector 🇧🇪
    • Encrypted Data Exchange
      • Internal
      • External
  • Customizable Features Module
    • Input Forms
    • Medical Records
    • Data Dashboards
    • Custom Connectors
    • Secure Log-in App
  • Support
    • Download
    • Contact Us
  • Advanced topics
    • Healthcare Data
      • Business intelligence
      • Anonymized Data
    • Encryption Key Creation and Storage
    • Multi-Master database replication
    • Cross Databases Sharing
    • Complex queries
Powered by GitBook
On this page
  • Introduction
  • The IPS Concept
  • The Dataset
  • Global Scope
  • FHIR IPS Implementation
  • SNOMED IPS Implementation

Was this helpful?

  1. Interoperability Module
  2. IHE IPS call

The IPS Concept

PreviousIHE IPS callNextFHIR API Data Exchange

Last updated 3 years ago

Was this helpful?

Introduction

IHE IPS a standardized report format for connecting with compatible EHRs, that has been codified with the an EU endorsed standard (EN 17269:2019). This addresses the issue of data exchange between isolated EHRs in a modern but also standardized way.

is part of their Clinical Documentation Architecture Product Series.

The IPS Concept

The IPS dataset is per its definition in EN 17269:2019 a minimal, non-exhaustive set of data elements required for the international patient summary.

‘Minimal’ reflects the ideas of ‘summary’ and the need to be concise, but also alludes to the existence of a core set of data elements that all health care professionals can use; it is intended to be a speciality agnostic and condition independent set. It does not imply that all the items in the data set will be used in every summary. It is also possible to refine the extract from a record such that the content of the summary is more relevant to a particular condition (e.g. asthma) but no asthma-specific elements will be specified in this standard. The IPS Document or IPS can be extended by non-IPS standard condition-specific data. ‘Non-exhaustive’ recognizes that the ideal data set is not closed, and is likely to be extended, not just in terms of requirement evolution, but also pragmatically in instances of use.

The Dataset

The International Patient Summary’ (IPS), defines a minimal dataset; one that is focussed upon the generic and important aspects of a person’s healthcare history to inform continuity of care between healthcare units. The data set library contains strict definitions of important patient healthcare aspects and the file contains the necessary information to achieve patient care handover.

Global Scope

The scope of IPS extends beyond the EU regulations and implementations are being developed for the global market, based on the guidance of HL7. This ensures future-forward compatibility to potential future data exchange requirements for iCure implementations.

FHIR IPS Implementation

SNOMED IPS Implementation

The standard or a sneak preview is available through the final draft before publication.

More exhaustive information can be found in the .

The FHIR IPS implementation is available on and is based on FHIR R4.

SNOMED CT has created that is IPS compatible and is a part of the free released by SNOMED Internation.

can be purchased from ISO
webpage of HL7 on IPS
Github
a subset
Global Patient Set
CEN/TC 251
For HL7, IPS
1MB
CEN _ TC 251 Final Draft.pdf
pdf
CEN TC 251 Final Draft before Standardization
IPS Standards in the HL7 SAIF Interoperability Matrix, source: HL7-IPS Project Page
source: HL7
source: HL7