HIP Clinical
Clinical applications that work with your data – not alongside it.
HIP Clinical comprises the clinical applications of the Health Intelligence Platform (HIP). Built on open standards, these applications integrate deeply with the platform without creating new dependencies. HIP Clinical applications work with the HIP CDR and other openEHR- and FHIR-compatible platforms.
Benefit
More time with patients. Less time with systems.
A complete patient view and structured documentation
The complete patient view
Applications such as the Patient Viewer and partner applications give clinical users access to the full data estate. Information documented natively in HIP Clinical applications on the basis of open standards is captured in a structured form and becomes immediately available to all connected applications – without duplicate entry or media breaks.
Challenge
The challenge at the point of care
Clinical teams work under time pressure and make decisions based on patient data distributed across multiple systems. Missing information is clarified by phone; information that is not available in structured form is recorded as free text or on paper. The consequences are duplicate documentation, time spent searching and the risk of overlooking information already available within the organisation.
The second part of the problem is the rigidity of the tools. When a department needs an additional field, a different view or an adapted form, it becomes a change request to a vendor – with effort, cost and a wait for the next release. In practice, care delivery then adapts to the software, rather than the software adapting to care delivery.
Solution
Applications that work with the shared data estate
Flexible for the requirements of your care delivery
With the Patient Viewer, HIP Clinical provides a core application for making all CDR data available to clinical users in an appropriate form. Dashboards can be configured individually to provide tailored views. Flexible integration options allow dashboards to be launched from external systems, such as the hospital information system, and embedded in workflows. Forms can also be created flexibly and integrated into existing workflows. Data is captured directly on the basis of open standards. Applications from the HIP ecosystem can be integrated quickly into the platform to implement use cases in workflow management, documentation, automation and beyond.
Because everything is built on open standards, individual applications remain replaceable. You can replace one component without changing the underlying data estate.
How HIP Clinical works
Applications read and write through the platform’s standardised openEHR and FHIR interfaces. A form writes its content into the clinical information model, where the Patient Viewer and every other application can read it immediately. This avoids the need for a second data store that would have to be reconciled, and prevents any one application from becoming the owner of data that other applications also need.
Access rights, audit logging and tenant separation originate in the data layer and apply consistently across all applications. What a user is permitted to see is determined not by the user interface, but by the data and the access rules of the data platform.
HIP Clinical makes the data stored in the CDR visible and usable for clinical users through applications. HIP Insights provides additional tools for analysing that data.
Your benefits
- The complete patient view in one place, with clinical context
- Structured documentation instead of free text and paper, without duplicate entry
- Adapt forms, views and dashboards yourself – without a change request or waiting for a release
- Access rights and audit logging from the data layer, applied consistently across all applications
- Built on open standards, with individual applications remaining replaceable
- Works with the HIP CDR or another openEHR- and FHIR-compatible data source
If you cannot adapt the user interface, care delivery adapts to the software.
Forms and views are configuration – not code.
In many healthcare organisations, every functional change becomes a process: define a requirement, commission it, pay for it and wait for the next release. This is not only costly; it changes the way people work. Departments stop submitting improvement requests, document outside the software and maintain their own lists. The quality of the data estate declines rather than improves.
HIP Clinical reverses this. Forms, views and dashboards are configured on the basis of the information models, and the change remains within the organisation. Because applications do not maintain their own data stores, the underlying data estate remains unchanged: a new view is a new view, not a new data source.
Key features
Patient Viewer
The view of the individual patient: brings together everything known about them across connected systems and presents it in clinical context. Clinical views and overviews for departments and roles are assembled from the available information models.
Clinical forms
Structured documentation based on the platform’s information models. Forms and fields are configured, not programmed. Provided as a partner component.
Consultation service
Clinical collaboration across sites and organisational boundaries, based on the same data foundation.
Clinical Dashboard Builder
Clinical views and overviews for departments and roles, assembled from the available information models.
Application ecosystem
A broad partner ecosystem for rapid, deep application integration with guaranteed data availability: AI-assisted clinical letter generation, workflow automation, virtual clinics, nursing documentation and more.
Open interfaces
All applications work through the platform’s openEHR and FHIR APIs. In-house and third-party applications use the same interfaces.
Data protection and regulatory assurance
Clinical environments require more than functionality. They require compliance. HIP Clinical meets both requirements:
- Access rights are enforced at the data level, not in the user interface. The data layer’s attribute-based access control applies consistently across all applications.
- Every read and write access is logged in accordance with IHE ATNA and can be reviewed by auditors.
- Deploy in an EU cloud or on premises: your data remains within the infrastructure you select.
- Regulated clinical products are provided by partners that assume responsibility as manufacturers.
HIP Clinical: Insights into the solutions
Visible, configurable and built on a shared data foundation.
Patient Viewer: a structured view of demographic and clinical patient data from the HIP.
Consultation service: a context-specific consultation request, including access to relevant patient data from the HIP.
Current use cases
The complete patient view at the point of care
Without switching systems or making calls
Make findings, prescriptions and clinical progress from multiple systems available in a single view, instead of searching across applications or requesting information by phone.Capture information in a structured form instead of free text and paper
Document once. Use many times.
Represent clinical documentation sheets as forms so that content is captured in a structured form and can be reused for care delivery, reporting and analytics.Collaboration across sites
Based on the same data foundation
Obtain specialist assessments across hospitals and departments without sending data or creating parallel data stores.As a clinician, I spend a significant part of my working day searching for information across ten to 20 different systems that do not communicate with one another – time that should really belong to my patients. HIP Clinical brings together data from every source precisely when I need it to make a decision at the bedside, making a real difference to the quality of care.
Designed for
Hospitals and hospital groups
Equip clinical teams with a complete patient view and enable them to adapt forms and views themselves, rather than commissioning those changes from a vendor.
Solutions for hospitals and hospital groupsSoftware providers
Build clinical products on an open, standards-based data foundation without developing persistence, permissions models and auditing yourself – and without the platform provider becoming a competitor in the regulated domain.
Solutions for software providersHealth regions and data spaces
Give clinicians across multiple organisations a shared view and shared documentation, with permissions for each organisation.
Solutions for health regions and data spaces