Based on Apache Camel as technology platform IPF provides a wide functionality including:
Transport adapters (HTTP, MLLP, SOAP, FTP, Mail, ...)
HL7 Domain Specific Language for easy message processing
Using IPF, one of the main contributors of the Open eHealth foundation implemented interfaces of several Actors in the IHE profiles PIX and PDQ. This implementation was successfully tested at the IHE Connectathons in Northern America and Europe.
IPF provides healthcare ICT vendors and user organizations a powerful tool to inte-grate their existing applications and products into an IHE conformant environment.
Healthcare Information Exchange Networks (HIEN) enables the exchange of medical information between different institutions. One of the biggest problems running a HIEN is the unique identification of the care providers like hospitals, health care professionals and so on. The solution to address this issue is the Provider and Organization Registry Service (PORS).
Similar to a Master Patient Index (MPI) PORS provides a unique Identifier for care providers. Within PORS a health care organization (HCO) like a hospital or a practice can be registered. Also a health care professional (HPC) can be registered with his demographics. A HPC can be assigned to one more HCOs. By querying PORS it can be figured out the unique ID of a HPC, HCO and to which organizations a HPC belongs to.
PORS is designed to fit into IHE based XDS compliant environments and the PORS Queries are based on HL7 V2 Syntax.
"The standard-based Consent Management Suite consists of two services.
The Consent Management Service (CMS) is able to receive and store consent documents.
It can receive queries concerning a dedicated patient consent, process it and return an answer.
Itrepresents a centralized policy enforcement point. The Consent Creator Service (CCS)
allows patients to create their consents electronically.
Interfaces to a Master Patient Index (MPI) and a provider index allow to dynamically generate
XACML-based policies which are stored in a CDA document to be transferred to the first service.
Three workflows have to be considered to integrate the suite into the PEHR:
recording the consent, publishing documents and viewing documents."
(Heinze et al. 2011)