Difference between revisions of "FHIR artifacts naming convention"
From Health Level 7 Belgium Wiki
(Created page with "== Profiles == * Profiles should be called according to the functionality, not necessarily for the base resource type. * Profile names should be prefixed with BE * Profile i...") |
m (→Profiles) |
||
| Line 9: | Line 9: | ||
# for prescriptions | # for prescriptions | ||
| − | The profiles would be: | + | The profiles for the examples above would be: |
* Medication Schedule: | * Medication Schedule: | ||
** Name: BEMedicationSchedule | ** Name: BEMedicationSchedule | ||
| Line 17: | Line 17: | ||
** Name: BEMedicationPrescription | ** Name: BEMedicationPrescription | ||
** id: be-medications-prescription | ** id: be-medications-prescription | ||
| − | |||
== Logical Models == | == Logical Models == | ||
Latest revision as of 15:12, 23 March 2020
Profiles
- Profiles should be called according to the functionality, not necessarily for the base resource type.
- Profile names should be prefixed with BE
- Profile ids should be prefixed with be-
- Example: MedicationRequest can be used for several purposes
- for the schedule / reminder of medications for a patient (let's call it "medicationschedule")
- for prescriptions
The profiles for the examples above would be:
- Medication Schedule:
- Name: BEMedicationSchedule
- id: be-medications-schedule
- Prescripton:
- Name: BEMedicationPrescription
- id: be-medications-prescription
Logical Models
Logical models should follow the same guidelines as Profiles, but the ids should be prefixed with model- instead of be-
