Transaction: Pharmaceutical Product Delivery
General information
STATUS:
Published
OWNER:
eHealth Platform
STANDARD:
KMEHR
VERSION:
2.0
DATE:
2009-11-10
DEFINITION:
The Pharmaceutical product delivery transaction aims to report the effective delivery of a product to the patient.
The work presented here results from the project Be-Prescript 3 that is being finalized.
STATUS:
Published
OWNER:
eHealth Platform
STANDARD:
KMEHR
VERSION:
2.0
DATE:
2009-11-10
DEFINITION:
The Pharmaceutical product delivery transaction aims to report the effective delivery of a product to the patient.
The work presented here results from the project Be-Prescript 3 that is being finalized.
Guidelines
Generalities
This transaction must, at least, be compliant with the KMEHR level 1. We recommend the use of a KMEHR message compliant with the KMEHR level 4 (see structure overview).
Transaction elements
| Element | Purpose |
|---|---|
|
id |
id of the transaction according to the ID-KMEHR convention. |
|
cd |
You must use the value 'productdelivery' from CD-TRANSACTION. You can always add your own local codes. |
|
date |
This is the date of delivery of the product. |
|
time |
This is the time of delivery of the product. |
|
author |
This is the physical person assuming the responsibility of the delivery. Only one physical healthcare party is allowed (possibly complemented by organisation and department). The ID-HCPARTY is mandatory. Additional information like name, address, phone are optional. |
|
redactor |
The redactor identifies the context of transcription or generation of the content of the transaction. It can identifiy a physicial person like a secretary, nurse, ... and possibly its department and/or organisation. It can also represent a robot for automatic content generation, an application for example. |
|
iscomplete |
If this is false, this means that you transfer only part of the information and that the recipient should expect a more complete version later. |
|
isvalidated |
If this is false, this means that the information has not been validated medically. |
Structure overview
You have the choice between:
text(s): to transfer your productdelivery as free text,
lnk(s): to encapsulate your productdelivery as a multimedia object (Word document for example),
item(s): to further structure your productdelivery.
We strongly recommend using items to build the this transaction.
Items
Any item of CD-ITEM could be used but we recommend more particularly the following ones:
| Item type (cd) | Item purpose | Item structure |
|---|---|---|
|
complementaryproduct |
This item should be used to deliver pharmaceutical products other than typical medications: 'eau de Cologne', bandages,... |
This item should be built in the exact way as medication. |
|
medication |
to describe each prescribed medication |
content (medicinalproduct | substanceproduct | compoundprescription) The element medicinalproduct identifies the prepacked medicinal product delivered. It is built using a national medecine code from CD-DRUG-CNK (element intendedcd) and a textual description (element intendedname). If the medicinal product is substituted the additional elements for a national medecine code from CD-DRUG-CNK (element deliveredcd) or a textual description of the substitued product (element deliveredname) are required. The element substanceproduct describes the INN or substance based cluster delivered. It is built using a INN cluster from CD-INNCLUSTER (element deliveredcd) and a textual description (element deliveredname). If the substance product is substituted the additional elements using an INN cluster from CD-INNCLUSTER(element deliveredcd) or a textual description of the substitued product (element deliveredname) are required. The element coumpoundprescription is a textual description of the coumpound delivery. |
| lifecyle
Must refer to the fixed value delivered of CD-LIFECYCLE. |
||
| [quantity]
Specifies the number of packages as a decimal number combined with a unit from CD-UNIT |
||
| [deliverydate]
Date of delivery of the product. |
Generalities
This transaction must, at least, be compliant with the KMEHR level 1. We recommend the use of a KMEHR message compliant with the KMEHR level 4 (see structure overview).
Transaction elements
| Element | Purpose |
|---|---|
|
id |
id of the transaction according to the ID-KMEHR convention. |
|
cd |
You must use the value 'productdelivery' from CD-TRANSACTION. You can always add your own local codes. |
|
date |
This is the date of delivery of the product. |
|
time |
This is the time of delivery of the product. |
|
author |
This is the physical person assuming the responsibility of the delivery. Only one physical healthcare party is allowed (possibly complemented by organisation and department). The ID-HCPARTY is mandatory. Additional information like name, address, phone are optional. |
|
redactor |
The redactor identifies the context of transcription or generation of the content of the transaction. It can identifiy a physicial person like a secretary, nurse, ... and possibly its department and/or organisation. It can also represent a robot for automatic content generation, an application for example. |
|
iscomplete |
If this is false, this means that you transfer only part of the information and that the recipient should expect a more complete version later. |
|
isvalidated |
If this is false, this means that the information has not been validated medically. |
Structure overview
You have the choice between:
text(s): to transfer your productdelivery as free text,
lnk(s): to encapsulate your productdelivery as a multimedia object (Word document for example),
item(s): to further structure your productdelivery.
We strongly recommend using items to build the this transaction.
Items
Any item of CD-ITEM could be used but we recommend more particularly the following ones:
| Item type (cd) | Item purpose | Item structure |
|---|---|---|
|
complementaryproduct |
This item should be used to deliver pharmaceutical products other than typical medications: 'eau de Cologne', bandages,... |
This item should be built in the exact way as medication. |
|
medication |
to describe each prescribed medication |
content (medicinalproduct | substanceproduct | compoundprescription) The element medicinalproduct identifies the prepacked medicinal product delivered. It is built using a national medecine code from CD-DRUG-CNK (element intendedcd) and a textual description (element intendedname). If the medicinal product is substituted the additional elements for a national medecine code from CD-DRUG-CNK (element deliveredcd) or a textual description of the substitued product (element deliveredname) are required. The element substanceproduct describes the INN or substance based cluster delivered. It is built using a INN cluster from CD-INNCLUSTER (element deliveredcd) and a textual description (element deliveredname). If the substance product is substituted the additional elements using an INN cluster from CD-INNCLUSTER(element deliveredcd) or a textual description of the substitued product (element deliveredname) are required. The element coumpoundprescription is a textual description of the coumpound delivery. |
| lifecyle
Must refer to the fixed value delivered of CD-LIFECYCLE. |
||
| [quantity]
Specifies the number of packages as a decimal number combined with a unit from CD-UNIT |
||
| [deliverydate]
Date of delivery of the product. |