The skill review-client-history as its source file smart-base/L4/skills/smart-l4/review-client-history.md writes it, rendered by gen-processes-viz.ts because 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 a health-worker lane. 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 records shown, each a FHIR resource (or a summary of a paper record), with its provenance: verified (a signature or a trusted source checked it), unverified (read but not checked) or reported (paper, or the client’s word); and the purpose of the visit.
  • Out: the reliedOn items, each with its provenance kept, and the gaps the health worker could not settle.

What the health worker does

  1. Read what bears on today’s care: allergies, current medicines, vaccinations, active problems.
  2. 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.
  3. 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.

input [1..1]output [1..1]subject [0..1]records [0..*]reliedOn [0..*]review-client-history«skill»review-client-historyinput : ReviewClientHistoryInput [1..1]output : ReviewClientHistoryOutput [1..1]ReviewClientHistoryInput«json-schema»ReviewClientHistoryInputsubject : ReviewClientHistoryInput.subject [0..1]purpose : string [0..1]records : ReviewClientHistoryInput.records[] [0..*]ReviewClientHistoryInput.subject«json-schema»ReviewClientHistoryInput.subjectreference : string [0..1]display : string [0..1]ReviewClientHistoryInput.records«json-schema»ReviewClientHistoryInput.recordsresource : object [0..1]summary : string [0..1]provenance : "verified" | "unverified" | "reported" [1..1]ReviewClientHistoryOutput«json-schema»ReviewClientHistoryOutputreliedOn : ReviewClientHistoryOutput.reliedOn[] [0..*]gaps : string[] [0..*]ReviewClientHistoryOutput.reliedOn«json-schema»ReviewClientHistoryOutput.reliedOnitem : string [1..1]provenance : "verified" | "unverified" | "reported" [1..1]

SMART Trust demonstrator: journeys J1 to J4 — built with folio-assistant.

deployed dev