diff --git a/schemas/med_dossier/Contraindication.yaml b/schemas/med_dossier/Contraindication.yaml index ba56b7f..fa8c639 100644 --- a/schemas/med_dossier/Contraindication.yaml +++ b/schemas/med_dossier/Contraindication.yaml @@ -5,10 +5,10 @@ required: properties: description: description: |- - If possible, normalized, but usually a coding unique to the source system or manually typed by a practicioner. + If possible, normalized, but usually a coding unique to the source system or manually typed by a practitioner. OPEN QUESTION: Given the unstructured nature of this field, contraindication does not appear usable to callers for anything - but showing it directly to a practicioner and hoping they know what it means. + but showing it directly to a practitioner and hoping they know what it means. type: string example: 'RAYNAUD, FENOMEEN' when: diff --git a/schemas/med_dossier/Correspondence.yaml b/schemas/med_dossier/Correspondence.yaml index 0f9602e..bb8185f 100644 --- a/schemas/med_dossier/Correspondence.yaml +++ b/schemas/med_dossier/Correspondence.yaml @@ -48,8 +48,8 @@ properties: A free-form textual description of the other party in this correspondence. type: string example: "Naar: Plastische chirurgie HMC, Den Haag" - practicioner: - $ref: 'Practicioner.yaml' + practitioner: + $ref: 'Practitioner.yaml' zorgdomein: description: |- If known and provided, The ZorgDomein message ID. ZorgDomein IDs are often used when referring a patient. Not all source systems provide these. diff --git a/schemas/med_dossier/Episode.yaml b/schemas/med_dossier/Episode.yaml index 99228fd..2748eea 100644 --- a/schemas/med_dossier/Episode.yaml +++ b/schemas/med_dossier/Episode.yaml @@ -40,6 +40,6 @@ properties: description: description: |- *OPTIONAL* Most HIS source systems default the 'description' of an episode to the standard description for the provided ICPC, but allow the - practicioner to change this description. + practitioner to change this description. type: string example: "Geboorte dochter" diff --git a/schemas/med_dossier/Feat.yaml b/schemas/med_dossier/Feat.yaml index f611206..04d4462 100644 --- a/schemas/med_dossier/Feat.yaml +++ b/schemas/med_dossier/Feat.yaml @@ -36,11 +36,11 @@ properties: Contents are free-form as it depends on the source system. type: string example: AA - practicioner: - $ref: 'Practicioner.yaml' + practitioner: + $ref: 'Practitioner.yaml' description: description: |- Some source systems allow adding a comment or description when registering a feat; often simply a copy of the description of - what `vektis` represents, but can be explicitly typed in by the practicioner registering this feat. + what `vektis` represents, but can be explicitly typed in by the practitioner registering this feat. type: string example: "12001: Dubbel consult huisarts" \ No newline at end of file diff --git a/schemas/med_dossier/Journal.yaml b/schemas/med_dossier/Journal.yaml index 946a78a..6591871 100644 --- a/schemas/med_dossier/Journal.yaml +++ b/schemas/med_dossier/Journal.yaml @@ -18,7 +18,7 @@ properties: description: |- *OPTIONAL* An ICPC1.1-NL code representing the problem / chronic illness that this journal note has been filed under. - In our experience the difference between `icpc` and `episode` are not well demarkated and practicioners do not necessarily use these fields + In our experience the difference between `icpc` and `episode` are not well demarkated and practitioners do not necessarily use these fields for their intended purpose. We suggest making no distinction between these 2 fields and accepting instead that this means journal text can have up to 2 ICPCs associated with them. type: string @@ -32,7 +32,7 @@ properties: example: "2015-05-01" s: description: |- - The journal text as typed by the practicioner for the 'S' field of SOAP (Subjective / Objective / Analysis / Plan). (Dutch: _S_ / _Subjectief_). + The journal text as typed by the practitioner for the 'S' field of SOAP (Subjective / Objective / Analysis / Plan). (Dutch: _S_ / _Subjectief_). A (transcription of the) description of the medical issue by the patient themselves. @@ -40,15 +40,15 @@ properties: type: string o: description: |- - The journal text as typed by the practicioner for the 'O' field of SOAP (Subjective / Objective / Analysis / Plan). (Dutch: _O_ / _Objectief_). + The journal text as typed by the practitioner for the 'O' field of SOAP (Subjective / Objective / Analysis / Plan). (Dutch: _O_ / _Objectief_). - The description of the medical issue as observed by a trained medical practicioner. + The description of the medical issue as observed by a trained medical practitioner. Can contain newlines, and can be quite long. For teleconsulting in particular, might be empty. type: string a: description: |- - The journal text as typed by the practicioner for the 'A' field of SOAP (Subjective / Objective / Analysis / Plan). (Dutch: _E_ / _Evaluatie_). + The journal text as typed by the practitioner for the 'A' field of SOAP (Subjective / Objective / Analysis / Plan). (Dutch: _E_ / _Evaluatie_). The diagnosis. @@ -56,7 +56,7 @@ properties: type: string p: description: |- - The journal text as typed by the practicioner for the 'P' field of SOAP (Subjective / Objective / Analysis / Plan). (Dutch: _P_ / _Plan_). + The journal text as typed by the practitioner for the 'P' field of SOAP (Subjective / Objective / Analysis / Plan). (Dutch: _P_ / _Plan_). The course of action to take, or notes about next steps to deal with the issue raised in this journal entry. @@ -64,14 +64,14 @@ properties: type: string x: description: |- - The journal text as typed by the practicioner for any non-SOAP field. + The journal text as typed by the practitioner for any non-SOAP field. Will be omitted if blank / not available. For source systems that do not work with the SOAP methodology, all journal text will be under this entry. Can contain newlines, and can be quite long. type: string - practicioner: - $ref: 'Practicioner.yaml' + practitioner: + $ref: 'Practitioner.yaml' type: description: |- A code representing of the style of consult: diff --git a/schemas/med_dossier/Measurement.yaml b/schemas/med_dossier/Measurement.yaml index 9586328..f1bac8a 100644 --- a/schemas/med_dossier/Measurement.yaml +++ b/schemas/med_dossier/Measurement.yaml @@ -45,7 +45,7 @@ properties: 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 practicioner or the specialist is the primary caregiver for chronic diabetes mellitus care) use the + 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. @@ -65,5 +65,5 @@ properties: type: string example: >- tekst Sensibilisatie voor algemeen voorkomende inhalatieallergenen (huisstofmijt, kat, hond, graspollen, boompollen, bijvoetpollen, kruidpollen) is op dit moment niet vastgesteld. - practicioner: - $ref: 'Practicioner.yaml' + practitioner: + $ref: 'Practitioner.yaml' diff --git a/schemas/med_dossier/Medication.yaml b/schemas/med_dossier/Medication.yaml index 1254e3c..9482283 100644 --- a/schemas/med_dossier/Medication.yaml +++ b/schemas/med_dossier/Medication.yaml @@ -12,7 +12,7 @@ properties: example: C03CA01 prescribed: description: |- - If present, the date when a practicioner prescribed this medication; possibly without actual medical review (e.g. just filing a refill request). + 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. @@ -32,7 +32,7 @@ properties: format: date example: "2023-03-28" prescriber: - $ref: "Practicioner.yaml" + $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), diff --git a/schemas/med_dossier/Practicioner.yaml b/schemas/med_dossier/Practitioner.yaml similarity index 87% rename from schemas/med_dossier/Practicioner.yaml rename to schemas/med_dossier/Practitioner.yaml index 29a1566..d23ba0e 100644 --- a/schemas/med_dossier/Practicioner.yaml +++ b/schemas/med_dossier/Practitioner.yaml @@ -1,5 +1,5 @@ description: |- - The medical practicioner (could be a doctor, an assistant, a chronic care specialist working at the GP, etc) who is responsible for entering this + The medical practitioner (could be a doctor, an assistant, a chronic care specialist working at the GP, etc) who is responsible for entering this information. Can be an assistant simply entering data from external sources; necessarily refers to somebody who works for the GP that is the source of this medical dossier. @@ -8,7 +8,7 @@ description: |- OPEN QUESTION: Would it be useful if this field is more structured and e.g. explains what it is, or that this field contains an ID that can be separately looked up using another API endpoint; we are very dependent on the source for the nature of this information, but some e.g. provide - the doctor under whose authority a practicioner is operating, which could be useful information. We can't guarantee that we can provide this data + the doctor under whose authority a practitioner is operating, which could be useful information. We can't guarantee that we can provide this data in a specific structure due to fundamental differences between HIS vendors, hence why right now this field is free-form. type: string example: AA \ No newline at end of file