The skill
review-client-historyas its source filesmart-base/L4/skills/smart-l4/review-client-history.mdwrites it, rendered bygen-processes-viz.tsbecause it has no instruction page on this site — do not edit here. All processes
Review the client’s history
Skill review-client-history: A health worker reads the client’s history as their device shows it (an International Patient Summary, imported records, or a paper card and what the client reports) and takes into account what bears on today’s care, weighing each item by where it came from: verified, unverified or reported. Input is the records with their provenance; output is what the health worker relies on.
Named by: J4.1 Read a family member’s records at the point of care abroad
Skill id:
review-client-history· Package:authoring-who-smart-guidelines· Performed by a person in ahealth-workerlane. The PHC digital transformation handbook’s “longitudinal tracking” of a health service user is what this reads.
Input and output
The contract is input.schema.json
and output.schema.json.
- In: the
recordsshown, each a FHIR resource (or a summary of a paper record), with itsprovenance:verified(a signature or a trusted source checked it),unverified(read but not checked) orreported(paper, or the client’s word); and thepurposeof the visit. - Out: the
reliedOnitems, each with its provenance kept, and thegapsthe health worker could not settle.
What the health worker does
- Read what bears on today’s care: allergies, current medicines, vaccinations, active problems.
- Treat each item by its provenance: an unverified or reported item is taken like paper, by the programme’s policy for paper records, never shown or recorded as verified.
- Note the gaps; the DAK’s own steps (decision support, a form) act on them.
Success criteria
- Nothing reported or unverified is relied on as verified.
- What was relied on, and why, can be read back from the output.
Input and output contracts
What this skill takes and gives, as a class diagram drawn from its JSON Schema contracts by the schemas viewer’s own renderer. Each box links to its definition; each type to its specification.