Draft. This page is unfinished. The mapping below comes from development notes and will be replaced with a more exact specification.
As from SFM version 3, a new representation for PLLinfo is included. Version 2 had only one (or none) objects for PLL/multidose info. Version 3 will have either:
none
one for each corresponding M25 message (M25.1, M25.2 and M25.3)
in the absence of M25 message(s), and with multidose responsible actors in M9.12: one stripped message containing info on relatedparties
SectionPLL
In case of no M25.x messages available by lookup AND md info in M9.12 or from KJ:
"entry": [
{
"reference": "urn:uuid:2ca6690f-47a3-4a40-8d86-6085e41629af",
"type": "http://ehelse.no/fhir/StructureDefinition/sfm-PLL-info",
"display": "M9.12"
}
]relatedparties: populate from RF.m912 or KJ.multidoseinfo (implemented in SFM-6030)
identifier: Message id from M9.6 when available, empty from KJ
code (.coding.code): “M9.12”, even when info is from KJ
code.text: “No M25 message available”
subject: patient from M9.12 if available
relatedParties will be populated with info on multidose responsibility. Pharmacy only will in this case indicate “Papirmultidose”.
In case one or more M25 messages are available:
getMedication: SFM shall populate all elements when present in lookup from RF or KJ.
sendMedication: SFM shall parse only the entry for M25.1, and ignore any other entry. Make sure that the relatedparties info from the M25.1 entry is correctly represented as Rolle elements in the resulting M25.1.
entry: reference shall be encoded to identify the three different types:
"entry": [
{
"reference": "urn:uuid:2ca6690f-47a3-4a40-8d86-6085e41629af",
"type": "http://ehelse.no/fhir/StructureDefinition/sfm-PLL-info",
"display": "M25.1"
},
{
"reference": "urn:uuid:2ca6690f-47a3-4a40-8d86-6085e416296d",
"type": "http://ehelse.no/fhir/StructureDefinition/sfm-PLL-info",
"display": "M25.2"
},
{
"reference": "urn:uuid:2ca6690f-47a3-4a40-8d86-6085e41629bc",
"type": "http://ehelse.no/fhir/StructureDefinition/sfm-PLL-info",
"display": "M25.3"
}
]For each entry
M25.1
relatedparties: populate from M25.1 EXCEPT multidose responsible pharmacy and doctor, which shall be from RF.m912 or KJ.multidoseinfo (implemented in SFM-6030)
deliveryinformation: Not present
text: top level comment from M25.1
substitute: Vikar from M25.1
createPLL (only present on sendMedication)
packinginfo: Not present
PLLdate: M25.1 timestamp
warning: any warnings from M25.1
medicationreview: from M25.1 Legemiddelgjennomgang when present (timestamp, performedby and comment). On sendMedication the extension on the bundle is written back to Legemiddelgjennomgang. performedby is a reference to a PractitionerRole in the bundle. next is not populated from M25.1.
identifier: Message id from M25.1
code: sfm-message-type
subject: patient from M25.1
author: the sender of the M25.1
M25.2
relatedparties: populate from M25.2 EXCEPT multidose responsible pharmacy and doctor, which shall be from RF.m912 or KJ.multidoseinfo (implemented in SFM-6030)
deliveryinformation: Not present
text: top level comment from M25.2
substitute: N/A
createPLL: N/A
packinginfo: from M25.2
PLLdate: M25.2 timestamp
warning: N/A
medicationreview: N/A
identifier: Message id from M25.2
code: sfm-message-type (M25.2)
subject: N/A
author: the sender of the M25.2
M25.3
relatedparties: populate from M25.3 EXCEPT multidose responsible pharmacy and doctor, which shall be from RF.m912 or KJ.multidoseinfo (implemented in SFM-6030)
deliveryinformation: Data from M25.3
text: top level comment from M25.3
substitute: N/A
createPLL: N/A
packinginfo: from M25.3
PLLdate: M25.3 timestamp
warning: N/A
medicationreview: N/A
identifier: Message id from M25.3
code: sfm-message-type (M25.3)
subject: N/A
author: the sender of the M25.3
More information on the mapping will be added here.