A jointly scoped pilot with agreed systems, examples and acceptance criteria.
Compare the FHIR versions, profiles and required resources of both systems
Implement a limited mapping with permissions in a test environment
Review references, missing data and examples confirmed by the responsible specialists
Scope, project price, schedule and required provider services are agreed before commissioning. Handover includes the agreed technical documentation and introduction.
Maintain one agreed technical interface through profile changes and transmission errors.
Technical takeover of the agreed existing solution
Agreed monitoring, troubleshooting and change maintenance
Documented handover of open issues and completed changes
Monthly price, allowance, service hours, term and cancellation are agreed separately. Infrastructure, licences and on-call support are included only when explicitly offered.
Use case, interface documentation and Implementation Guides
Synthetic examples and a subject specialist responsible for data meaning
A description is enough for your first enquiry. We will then agree suitable ways to exchange files and arrange access.
What the scope covers
The pilot uses synthetic data. Production health data, clinical validation, medical device assessment and any applicable gematik requirements need a separately clarified scope. No diagnostic or treatment decisions are included.
We check the package against your project. Your enquiry is non-binding; commissioning and scheduling are agreed afterwards.
UNDERSTAND THE TOPIC
FHIR support does not automatically make two applications compatible.
HL7 FHIR describes the electronic exchange of health information. Applications may nevertheless support different versions, profiles and resources. A shared use case establishes which parts actually need to work together.