README.md

Salford Renal PROMS and COPD self monitoring import

Scope of Work

1. Create openEHR models as a target to receive patient-derived Renal PROMs XML input.
2. Create openEHR models as a target to receive patient-derived COPD management XML input.

Renal PROMs

1. Analyse the OPTE_PRO xml input example and associated schema. This is a feed from a system holding Renal medicine-related PROMs information.
2. Create an openEHR template as a target for importing the OPTE_PRO input xml document.
3. Identify existing openEHR archetypes and create new archetypes (reusable where possible) to be used within the openEHR template.
4. Create a mapping guidance document for the input xml to an openEHR FLAT JSON composition.
5. Create associated artefacts e.g. A sample FLAT JSON instance, Marand web template document.

Output

Reused existing international archetypes

• Report | openEHR-EHR-COMPOSITION.report.v1
• EQ_5D_5L | openEHR-EHR-OBSERVATION.eq_5d_5l.v0 (Not in international CKM for licensing reasons.)

New archetypes

• PAM-13 score | openEHR-EHR-OBSERVATION.pam_13.v0
• POS-S Renal score | openEHR-EHR-OBSERVATION.pos_s_renal.v0

It is intended that these will be uploaded/published to the international openEHR CKM.

New templates

• Salford Renal PROMs Import Report - Salford Renal PROMs Import Report.v0

Mapping guidance / technical artefacts

• Renal PROMS Mapping Guidance document
• Example target RENAL PROMS Import FLAT JSON (Sample composition data) instance
• Salford Renal PROMs Import Report Operational template (Use for upload to CDR)
• Salford Renal PROMs Import Report - Web template (Json variant of operational template)

COPD Self Reported Observations

1. Analyse the COPD Self Reported Observations XML example and associated schema. This is a feed from a system holding patient device information relating to COPD.
2. Create an openEHR template as a target for importing the COPD input xml document.
3. Identify existing openEHR archetypes and create new archetypes (reusable where possible) to be used within the openEHR template.
4. Create a mapping guidance document for the input xml to an openEHR FLAT JSON composition.
5. Create associated artefacts e.g. A sample FLAT JSON instance, Marand web template document.

Output

Reused existing international archetypes

• Report | openEHR-EHR-COMPOSITION.report.v1
• Pulse oximetry | openEHR-EHR-OBSERVATION.pulse_oximetry.v1
• Pulse / Heart beat | openEHR-EHR-OBSERVATION.pulse.v1
• Blood Pressure | openEHR-EHR-OBSERVATION.blood_pressure.v1
• Body temperature| openEHR-EHR-OBSERVATION.body_temperature.v2
• Story | openEHR-EHR-OBSERVATION.story.v1.adl

New local archetypes

• COPD Salford COPD Questions | openEHR-EHR-CLUSTER.salford_copd_questions.v0.adl

New templates

• COPD Self Reported Observations - Salford COPD Self Reporting.v0

Mapping guidance / technical artefacts

• COPD Self Reported Observations Mapping Guidance document
• Example target COPD Self Reported Observations FLAT JSON (Sample composition data) instance
• COPD Self Reported Observations - Operational template (Use for upload to CDR)
• COPD Self Reported Observations - Web template (Json variant of operational template)