type: object
required:
  - code
  - when
  - value
properties:
  wcia:
    description: |-
      NHG-standardized WCIA (Werkgroep Coördinatie Informatie Automatisering) code (describes the nature of the measurement),
      as listed on [Webtools NHG labcodeviewer](https://bepalingen.nhg.org/labcodes/determinations), under column 'Nr.'.
    type: number
    example: 1872
  code:
    description: |-
      NHG-standardized labcode (describes the nature of the measurement), as listed on
      [Webtools NHG labcodeviewer](https://bepalingen.nhg.org/labcodes/determinations).
      The full memo+mat+bijz code is provided with no separation.
      
      If the source allows custom labcodes, this value can contain a non-NHG-standard code. Most source systems do allow this.
      
      Guaranteed to be provided, and will never be blank.
      
      OPEN QUESTION: Would it be more convenient if this API guarantees the provided code is NHG compatible, relying on the `source_code` field
      to represent such custom codes?
      
      OPEN QUESTION: Would it be more convenient if this API provides this code separated out into memo/mat/bijz, e.g. "KREA O MK" instead of "KREAOMK"?
    type: string
    example: KREAOMK
  source_code:
    description: |-
      If the source system uses a different code to represent this measurement in its own system, it is listed here.
      
      If present, guaranteed to be different from `nhg_code`. For example, a GPIS might use `ROKENHG` instead of NHG-standard `ROOKAQ` to
      represent registration of patient's smoking behaviour.
    type: string
    example: ROKENNHG
  when:
    description: |-
      Date when this measurement was done. In practice it may instead represent the date when the measurement was registered
      which might be a day or two after the measurement was actually performed; not all source systems make it possible to
      distinguish the nature of the date.
    $ref: ../date.yaml
  value:
    description: |-
      The value of the measurement. Normalized and NHG compatible if possible. For example, enumerated values (such as for `DMHBKZ` which
      represents whether the general practitioner or the specialist is the primary caregiver for chronic diabetes mellitus care) use the
      NHG numeric answer codes (in `DMHBKZ`'s case, `"48"` is returned if the GP is the primary caregiver, and `"49"` if the specialist is).
      
      If the source provides a value that is not understood by ZOO's normalizers, the source value is provided verbatim.
      
      This value can be blank; various labcodes simply represent that an act was performed and do not register any result.
      
      If the value is numeric (for example, systolic blood pressure: `nhg_code = "RRSYKA"`), the dot is used as fractional separator, regardless
      of what the source has provided.
    type: string
    example: 48
  comment:
    description: |-
      Some source systems allow adding a comment to any measurement; if one is present, it is provided here.
      
      Note that these can be quite lengthy, as sometimes a lab will add standard boilerplate text about how to interpret
      the result in these fields.
    type: string
    example: >-
      tekst Sensibilisatie voor algemeen voorkomende inhalatieallergenen (huisstofmijt, kat, hond, graspollen, boompollen, bijvoetpollen, kruidpollen) is op dit moment niet vastgesteld.
  practitioner:
    $ref: 'Practitioner.yaml'