A connected-health data handover worksheet
A field dictionary, example records and failure-state matrix for connected-health data handovers.
Read the resourcesectors
Connected health and software
Define the data, versions, failure states and responsibilities behind a connection before relying on the information it carries.
Follow the information
Map where data is generated, transformed, transmitted, stored, displayed and reused. A field name alone does not establish meaning: record the unit, timestamp, time zone, source, calculation, valid values and version.
Make absence visible
The receiving system should be able to distinguish no observation, a failed measurement, a delayed message, information withheld for another reason and a corrected value. Define how each state appears and whether an earlier value remains visible.
Assign the interface
Identify who maintains the schema, announces a change, tests compatibility, investigates discrepancies and supports the user. A working technical connection does not settle ownership of every downstream decision.
Use the handover worksheet
Describing the purpose of a health product
A blank worksheet and worked example for defining a health product's configuration, users, setting, input, output and intended action.
Read the resourceBring a data question
Describe the sending product, receiving system, data purpose and failure or change you want to examine. Do not include credentials, access tokens or personal health data.