You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
63 lines
3.2 KiB
YAML
63 lines
3.2 KiB
YAML
type: object
|
|
required:
|
|
- atc
|
|
properties:
|
|
atc:
|
|
description: |-
|
|
An [Anatomical Therapeutic Chemical (ATC)](https://en.wikipedia.org/wiki/Anatomical_Therapeutic_Chemical_Classification_System) level 5 code.
|
|
|
|
OPEN QUESTION: Is it convenient to also send the dutch and/or english commonly accepted name for this ATC code? Feels wasteful in an API.
|
|
type: string
|
|
format: '^[A-Z]\d{2}[A-Z]{2}\d{2}$'
|
|
example: C03CA01
|
|
prescribed:
|
|
description: |-
|
|
If present, the date when a practitioner prescribed this medication; possibly without actual medical review (e.g. just filing a refill request).
|
|
Depending on how the medication was dispensed, some dispensing entities (e.g. pharmacies) are linked with source systems and will cause a
|
|
medication record to be registered that has no prescriber or prescription date (because it wasn't prescribed; at least, not by this GP office),
|
|
but was picked up by the patient.
|
|
|
|
We advise coalescing `prescribed` and `delivered`, as this guarantees an actual date.
|
|
$ref: ../date.yaml
|
|
delivered:
|
|
description: |-
|
|
If present, the date when the patient received this medication (usually, because they picked it up at a pharmacy). Not all pharmacies are
|
|
linked to source systems and therefore, a blank value for `delivered` _may_ mean the prescription was never filled, or it _may_ mean the
|
|
entity that filled the prescription does not relay this to the source system.
|
|
|
|
At least one of `prescribed` and `delivered` is guaranteed to have a value.
|
|
$ref: ../date.yaml
|
|
prescriber:
|
|
$ref: "Practitioner.yaml"
|
|
end:
|
|
description: |-
|
|
The medication is intended to last the patient no further than this date, if present. If source system doesn't send this date (not all do),
|
|
an estimate based on the nature of the medication and the suggested dosage.
|
|
|
|
If not present, this isn't the kind of medication that is designed to be used until symptoms fade or is no longer needed, or,
|
|
our normalization systems aren't capable of normalizing the dosage/form into a meaningful end date.
|
|
$ref: ../date.yaml
|
|
description:
|
|
description: |-
|
|
This field is usually initialized with a general dutch name for the medication, but can be overwritten with custom text by the prescriber.
|
|
|
|
Can describe the general medication or the specific brand name; it varies considerably between source systems.
|
|
type: string
|
|
example: "CUTISOFT NWK ST 10X10 48851"
|
|
pharmacy:
|
|
description: |-
|
|
If automatically sent to a specific pharmacy, some source-system custom coding that indicates which pharmacy it was sent to.
|
|
type: string
|
|
example: AN
|
|
usageCode:
|
|
description: |-
|
|
A coded description of how to use this medication. Depends on source GPIS; sometimes even on the individual configuration of
|
|
a practice's GPIS or that practice's regional server; these values aren't normalized, and sometimes not available at all.
|
|
type: string
|
|
example: 1D1T
|
|
usageText:
|
|
description: |-
|
|
Human-readable (dutch) description of how to use this medication. Depends on source GPIS and often not available at all.
|
|
type: string
|
|
example: Gebruik bekend
|