...
Theme | Observations |
Initiative | HOB001 - Patient recorded observations from Helm to System of Systems |
User Journey Summary | Patient captures and records personal observations in Helm. |
Information provider roles | Patient, citizen |
Information consumer roles | GP, practice nurse, care coordinator, secondary care clinician |
Supporting Work | |
Alignments / Support | |
Diagram | |
FHIR profiles and resource mapping
Observation data will conform to the following FHIR profile:
https://www.hl7.org/fhir/STU3/observation.html
Observations are a central element in healthcare, used to support diagnosis, monitor progress, determine baselines and patterns and even capture demographic characteristics. Most observations are simple name/value pair assertions with some metadata, but some observations group other observations together logically, or even are multi-component observations. Note that the DiagnosticReport resource provides a clinical or workflow context for a set of observations and the Observation resource is referenced by DiagnosticReport to represent lab, imaging, and other clinical and diagnostic data to form a complete report.
Uses for the Observation resource include:
Vital signs such as body weight, blood pressure, and temperature
Laboratory Data like blood glucose, or an estimated GFR
Imaging results like bone density or fetal measurements
Devices Measurements such as EKG data or Pulse Oximetry data
Clinical assessment tools such as APGAR or a Glasgow Coma Score
Personal characteristics: such as eye-color
Social history like tobacco use, family support, or cognitive status
Core characteristics like pregnancy status, or a death assertion
Mandatory and Must Support Data Elements
The following data-elements are mandatory (i.e data MUST be present) or must be supported if the data is present in the sending system (Must Support definition). They are presented below in a simple human-readable explanation. Profile specific guidance and examples are provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements.
Each Observation must have:
a patient (as subject)
a date and time
a unit
a value
Each Observation may have:
a note
Examples
Example 1
Example 2
Example 3
[FHIR DIAGRAM]
UI design guidance
...
To dobe elaborated during construction sprints:
Wireframes of web and mobile views
UI control elements - Getting input, navigation, data display / content structuring
Advanced UI elements - History, provenance (multi-data point rendering), summary/detail, graphing UI
Clinical terminology and coding
...