This scenario represents the key clinical information typically recorded and updated as part of routine monitoring of patients who are on chemotherapy.
Detailed description of scenario
-
A Code4Health Ehrscape domain with access to the Marand EhrExplorer view of the c4h_ripple_rcm domain. This will allow templates to be viewed and AQL queries to be constructed.
-
A Workspace.md file containing details of key domain identifiers and assets e.g. dummy patient identifiers, template names, login and password details for the c4h_rcm domain.
-
A local repository of openEHR archetypes and templates. These archetypes and templates have assembled partly from remote repositories such as the openEHR Foundation CKM repository, or UK Clinical Models repository. Other artefacts, in particular the openEHR templates, have been authored locally and are maintained along with copies of the required archetypes in this Git repository. The key template is ..
Ripple RCM Patient Monitoring Report- the regular report sent by the patient to the monitoring unit.The ‘operational templates’ (effectively the compiled version of each template) have been uploaded to the RCM domain along with some dummy data, with the instance examples being available.
The templates are most easily viewed via the Marand EhrExplorer tool.
-
A Postman Collections file which can be imported to provide easy access to the Code4Health Ehrscape API.
-
A Postman Environment file for the
c4h_ripple_rcm domain, containing a number of preset variables. -
A Technical tasks guide, describing the key tasks involved in getting up and running with Ehrscape for this clinical scenario
-
An Overview of openEHR and Ehrscape guide for those new to openEHR concepts.