diff --git a/schemas/fundus-status.yaml b/schemas/fundus-status.yaml index b51e540..a003c25 100644 --- a/schemas/fundus-status.yaml +++ b/schemas/fundus-status.yaml @@ -181,4 +181,41 @@ properties: type: string nhgResult: type: integer - format: int32 \ No newline at end of file + format: int32 + followup: + type: object + description: Contains information about advice given to patient about scheduling future fundus inspections (aka fundus followup). + properties: + nhgResult: + description: |- + The followup advice, in NHG answercode for `FSFUFZ` form, regardless of how this followup advice was registered: + * `326` – within 1 day with a specialist + * `325` – within 1 week with a specialist. + * `324` – within 1 month with a specialist. + * `323` – within 3 months with a specialist. + * `566` – within 6 months with a specialist. + * `322` – regular scheduling at 1 year frequency. + * `386` – regular scheduling at 2 year frequency. + * `565` – regular scheduling at 1 year frequency. + * `619` – No fundus checkup required. + type: integer + format: int32 + enum: [326, 325, 324, 323, 566, 322, 386, 565, 619] + nhgCode: + description: |- + If present, the NHG memocode used to register the followup advice. Will be in the terms dictionary. + type: string + example: FSFUFZ + timestamp: + $ref: "date.yaml" + description: Date when this followup advice was registered. + before: + $ref: "date.yaml" + description: |- + The fundus followup advice indicates fundus needs to be done at or before this date. + + Determined by taking the last time fundus checkup was performed based on e.g. a `DMR7FALI` measurement, and adding the followup advice time + to that date. If no fundus inspection has been done yet, the date at which the followup advice was given, plus the time indicated in the followup + advice, is provided (e.g. if on April 5th the followup advice is 'within one month', this value will be 'May 5th'). + + Will be the sentinel value 'Jan 1st, 9999' if no followup advice is needed.