- Deploying to test requires that you have a backup file around so find one you'd like to use
- ./bin/deploy_test.sh /full/path/to/backup # The script moves around a bunch so relative paths will fail
elCID reads data from a number of upstream systems:
- Cerner Demographics
- Cerner Appointments
- Cerner Encounters
- Winpath Labs
- Freenet ICU Handover
The mechanics of communicating with upstream databases is handled by
the intrahospital_api module, which exposes some interfaces for making
queries, and creating patients.
The appointment, encounters and ICU integrations are self-contained within their
respective plugins and use the intrahospital API to initiate creating
a patient and configuring connections to upstream databases.
The lab and demographic integrations are split between the elcid, intrahospital_api and plugins.labtests modules.
The Covid 19 plugin also contains some utilities for querying upstream lab data taking into account incidental implementation details of how 'Covid positive' is reported.
The Covid 19 plugin also fetches patients who are tested for covid and adds them to the elCID cohort
elCID writes data to an upstream database provided by the RFH integration team. This is populated with:
- results summaries for ICU patients, which is then displayed on the ICU handover database (Cron)
- Clinical advice entries, triggered by certain save events in elCID
The intrahospital_api package exposes the function
create_rfh_patient_from_hospital_number(hospital_number, episode_category)
which ensures that a patient will have their integrations set up correctly.
Keeping data in elCID in sync with upstream sources is done via periodic tasks run by cron jobs on the server.