http://fhir.patientsknowbest.com/structuredefinition/aggregated-medicationstatement
https://www.hl7.org/fhir/R4/medicationstatement.html
Description
This profile is…
a description of how non-FHIR medication data will be mapped to FHIR in the Aggregated FHIR endpoint by PKB
This profile is not…
a spec for all Medication and MedicationStatement resources returned from the Aggregated FHIR endpoint; resources sent to a Customer FHIR endpoint are not guaranteed to conform to this profile
a spec describing how Medication and MedicationStatement resources must be sent to a Customer FHIR endpoint; some of the elements used in this profile might only be meaningful for migrated data and cannot be provided to a Customer FHIR endpoint
Relevant PKB entities
FHIR | PKB | Notes |
---|---|---|
Resource id | [[Medication.Aggregated Data Point ID]] | |
Resource meta |
[[Data Point.Privacy Label]] code mappings (PKB → FHIR):
| |
| A single uploadeddata entry can result in multiple data points, so this ID does not necessarily uniquely identify a data point. | |
| ||
| ||
| ||
| ||
| Note that this is a reference, unlike the meta.security which contains a code. | |
| Note that this is a reference, unlike the meta.security which contains a code. | |
| Note that this is a reference, unlike the meta.security which contains a code. | |
| ||
| ||
| ||
| ||
| ||
MedicationStatement.extension | For each [[Medication.Attachment]]:
| |
| The “Resolve()” notation indicates that the display value for the corresponding specialty code will be determined at the time of retrieval, based on the (optional) code set for the source organisation. | |
| ||
MedicationStatement.identifier |
| |
| ||
MedicationStatement.status |
| |
MedicationStatement.medicationCodeableConcept | [[Medication.Substance]] | |
MedicationStatement.effectivePeriod |
| |
MedicationStatement.subject |
| |
MedicationStatement.dosage |
[[Medication.Frequency Units]] code mappings (PKB → FHIR):
| Note #1: PKB supports more than one for dose units, but Quantity can represent only one. To ensure data is not lost, an extension is returned with the full CodeableConcept. Note #2: Frequency instructions of “as directed” are discouraged, but if they have been provided then “As directed” will be set into the timing.code.text element. |