Gravitate Health FHIR Implementation Guide, published by Gravitate Health Project. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/gravitate-health/ and changes regularly. See the Directory of published versions
Project Workflow
ePI Focusing
The current app and backend is developed to work like this:
patient patient Frontend Frontend Backend Backend EHR EHR Registration register create profile get ips <URL>/Patient?$summary={identifier} usage presents medication list based on ips asks for information for specific one drug gets medication resource code searchs for epi using code as identifier for Medicinal Product <URL>/Composition? _language=<lang> &category=R&identifier=<code> gets id returns epi bundle focusing ask for focusing <URL>/focusing/focus/<bundle> ?preprocessors=preprocessing-service-manual &lenses=<lenses> &patientIdentifier=<pat_id> returns epi bundle checks lenses in extension ask for lenses description and metada <URL>/fhir/Library?_id=<l1>,<l2>,.. OR Have lenses in the first response OR have cache of lenses already returns lenses description and metadata in a searchset checks data on extensions per section for aditional data. uses lenses and epi data to render the focused epi bundle with explanation
ePI Full Focusing
Since this can also be implemented with server or client side focusing, we can also have:
user user system X system X G-Lens-On-FHIR G-Lens-On-FHIR FocusingManager FocusingManager FOSPS Infrastructure FOSPS Infrastructure National infrastructure National infrastructure alt [case 1 - full data] highlight ePI send full preprocessed ePI + full IPS full preprocessed ePI + full IPS focus return focused ePI return focused ePI [case 2 - only ID's data] highlight ePI send full preprocessed ePI + full IPS only send ePI ID + patient ID from IPS fetch stored IPS fetch stored ePI focus return focused ePI return focused ePI [case 3 - federated fetch] highlight ePI only send ePI ID + patient ID from IPS only send ePI ID + patient ID from IPS Fetch IPS Fetch ePI focus return focused ePI return focused ePI [case 4 - hybrid federated fetch] highlight ePI only send ePI ID + full IPS only send ePI ID + full IPS Fetch ePI focus return focused ePI return focused ePI
ePI Focusing With List
With Lists, the workflow should be:
patient patient Frontend Frontend Backend Backend Registration register create profile get ips <URL>/Patient?$summary={identifier} Usage presents medication list based on ips asks for information for specific one drug gets medication resource code searchs for epi using code as identifier for Medicinal Product <URL>/List?subject.identifier=<code> gets bundle and composition for language <language> and category == "R" <URL>/Bundle?_list.identifier=<code> &_language=<language> &composition.category=R focusing ask for focusing <URL>/focusing/focus/<bundle> ?preprocessors=preprocessing-service-manual &lenses=<lenses> &patientIdentifier=<pat_id> <URL>/Bundle?_list.identifier=<code> &_language=<language> &composition.category=P returns epi bundle
The Gravitate Health project has received funding from the IMI 2 Joint Undertaking under grant agreement No 945334.
