Background
Problem statement
It
Regular measurements throughout the day - trend data
Home observations more representative compared to those taken in a clinical setting
Blood pressure
Peak flow meter measurements (time, free text comments)
Weight
Context of use
Settings and roles
Summary Flow
To do - Visualisation of data from capture to presentation. [image links inline]
Patient capture of an observation using tools in the home.
Patient entry of observation data into Helm.
FHIR mapping in SoS
UI presentation in Helm with historical data.
UI presentation in YHCR Care Portal (based on Helm panel above) - with additional functionality for clinician views
Clinician roles and workflows
Target Systems Development
Develop interface (based on both technical and functional requirements) to display the answers to WMTM questions in Helm (Person Held Record) that have been authored by professionals in other settings and subsequently shared via YHCR / SoS.
Develop interface to both capture and display answers to WMTM questions in the YHCR Care Portal that have been authored by professionals in other settings and subsequently shared via YHCR / SoS. This will be based on work completed in Helm as it shares the same architecture.
Support the development of the user interface within the Leeds Care Record (LCR) in order to present WMTM answers derived via YHCR / SoS.
User journeys
Theme | Questionnaire Sharing |
Initiative | HQ001 - Helm questionnaires shared with professionals |
User Journey Summary | Patient/homelessness peer capture of ‘What Matters to Me’ questions in Helm for sharing with professional users via YHCR Portal (and any other SoS connected consumers). |
Information provider roles | Patient, citizen, homelessness peer advocate |
Information consumer roles | GP, practice nurse, care coordinator, secondary care clinician |
Supporting Work | Alignment to PRSB standards, NHSI/E co-design groups for personalised care. |
Alignments / Support | ICS priorities for personalised care and inclusion agenda (Bevan) |
 | |
FHIR profiles and resource mapping
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 Questionnaire must have:
a narrative summary of the questionnaire
a status
an intent
a category code of “”
a patient
Examples
Example 1
Example 2
Example 3
...
UI design guidance
To do:
Wireframes of web and mobile views
UI control elements - Getting input, navigation, data display / content structuring
Advanced UI elements - History, provenance, summary/detail