CH EMED EPR
2.0.0 - trial-use
This page is part of the FHIR eMedication exchange formats for the implementation effort of CARA within its EPR community (v2.0.0: STU2) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Comments consisting of free text can be added to the different resources of the eMedication service. It is important to note that depending on the resource to which the comments are attached, the aggregation rules of the eMedication service might produce different results when fetching a PMLC document.
Comments (as many as desired) might be attached to an MTP medication statement by filling a note.text
element per comment.
Note that neither the note.author
nor the note.time
elements are expected to be present. If present, these will be ignored by the aggregator. The author is always assumed to be the informationSource
and the time is assumed to be the dateAsserted
.
Comments added to an MTP document's medication statement will be added as comments to the newly created treatment (globally).
Comments (as many as desired) might be attached to a PRE medication request by filling a note.text
element per comment.
Note that neither the note.author
nor the note.time
elements are expected to be present. If present, these will be ignored by the aggregator. The author is always assumed to be the requester
and the time is assumed to be the authoredOn
time.
Comments added with a PRE document's medication request are added to the treatment instance created by the new medication request.
Note that the first medication request to be added to a treatment will effectively replace the first/base treatment instance that was created with the original MTP document.
Comments (as many as desired) might be attached to a DIS medication dispense by filling a note.text
element per comment.
Note that neither the note.author
nor the note.time
elements are expected to be present. If present, these will be ignored by the aggregator. The author is always assumed to be the performer
and the time is assumed to be the whenHandedOver
time.
All comments (attached to the observation or to the changed medication statement or request) are added to the target of the medication dispense:
All PADV documents must contain an Observation, which accepts only one comment to be attached by filling the note.text
element.
Note that neither the note.author
nor the note.time
elements are expected to be present. If present, they will be ignored by the aggregator. The author is always assumed to be the performer
and the time is assumed to be the issued
.
This comment conveyed with the observation note conveys the only comment that is allowed to be added with a PADV COMMENT. For any other PADV, the note contains the reason for the PADV. In both cases the comment is treated as any other comment by the aggregator.
PADV CHANGE documents are allowed to provide more comments by filling them within the changed medication statement or changed medication request resource. The rules for the changed resources comments are the same as for their original counterparts.
All comments (attached to the observation or to the changed medication statement or request) are added to the target of the PADV:
When producing the PMLC, the eMedication service will use the aggregated data to attach the stored comments as follows:
All medication statements within a PMLC correspond to a treatment instance and contain all the treatment (global) comments as well as the treatment instance comments. Each comment will be added as an element within the note
element of the PMLC medication statement:
note.text
: the comment itself, as free text.note.time
: the timestamp of when the comment was done. See the other resources descriptions in this guide to see what the aggregator uses to determine the comment timestamp.note.author
: the author of the comment. See the other resources descriptions in this guide to see what the aggregator uses to determine the authorship.Given the following sequence:
Assuming that both prescriptions are still valid, a PMLC produced after the previous steps would contain two medication statements (for said treatment), one for each existing treatment instance/line:
Let's assume that the following extra step happens:
After this extra step, and assuming that both prescriptions would still be valid, the PMLC would see again two medication statements (for said treatment):