# {{page-title}}

A prescription is a resource of type `Bundle` containing a `CarePlan` for the prescription and several `ServiceRequest` as prescription lines. Additional resources may be added in the `Bundle` to provide more information. 

A full example can be found [here](https://simplifier.net/ePrescriptionLux/Bundle-labo-presc-post/~json). 

## The prescription Bundle

The prescriber's software creates a transaction [Bundle](https://simplifier.net/eprescriptionlux/eplabprescriptionbundle):
{{tree:https://www.esante.lu/fhir-spec/StructureDefinition/EPLabPrescriptionBundle}}

The `Bundle` is a conatainer to provide all resources (in `Bundle.entry`) that are part of the prescriptipon, i.e.:
- The prescription document
- Each prescription line
- The patient
- The prescriber
- The optional consent for subcontrators to send to the DSP
- The PDF document of the prescription
- Information about copies to send
- Information about practitioners that shall receive the copies

## The prescription document

A prescription document is represented by a [CarePlan](https://simplifier.net/eprescriptionlux/eplabprescription) included in a `Bundle` :
{{tree:https://www.esante.lu/fhir-spec/StructureDefinition/EPLabPrescription}}

In the extensions, there are fields for the patient and fulfiller instructions, to give any indications or information about the patient, the analysis, ... that are valid **for the whole prescription**. Specifics for a line are given on the prescription line.

`CarePlan.activity` contains references to the prescription lines.

## The prescription lines

Each [ServiceRequest](https://simplifier.net/eprescriptionlux/eplabprescriptionline) represents a prescription line:
{{tree:https://www.esante.lu/fhir-spec/StructureDefinition/EPLabPrescriptionLine}}

`ServiceRequest.orderDetil` is used to give information for tha lab specific to this line.  `ServiceRequest.patientInstruction` has the same purpose but for the patient.

## The patient

The patient is a resource of type [Patient](https://simplifier.net/eprescriptionlux/eppatient):
{{tree:https://www.esante.lu/fhir-spec/StructureDefinition/EPPatient}}
It contains the patient information as known by the prescriber.

## The prescriber

The prescriber is a resource of type [Practitioner](https://simplifier.net/eprescriptionlux/eppractitioner):
{{tree:https://www.esante.lu/fhir-spec/StructureDefinition/EPPractitioner}}. It contains the prescriber information as provided by its own system.

## The health professionals recipients of the result

Each health professional is represent by a specific type of [Practitioner](https://simplifier.net/eprescriptionlux/eppractitionerunk) :
{{tree:https://www.esante.lu/fhir-spec/StructureDefinition/EPPractitionerUnk}}
This is not to confuse with the prescriber that SHALL be represented as specified before.

## The consents

For the moment, only one type of consent is used : whether or not the subcontractor shall send the document to the DSP. See {{pagelink:consents}} for details.
It is represented using a TODO

## The PDF document

This is simply the base64 of the prescription, transmitted using a [DocumentReference](https://simplifier.net/eprescriptionlux/eplabdocumentref):
{{tree:https://www.esante.lu/fhir-spec/StructureDefinition/EPLabDocumentRef}}

## The copies to send

Using an optional [CommunicationRequest](https://simplifier.net/eprescriptionlux/epcommunicationrequest), it is possible to mention the patient, and many health professional as recipients of the result. The prescriber SHALL NOT be present as he will always receive the result.
{{tree:https://www.esante.lu/fhir-spec/StructureDefinition/EPCommunicationRequest}}
For the patient, you SHALL reuse the `Patient` resource used anyway in the prescription.
For health professional, take care to used the right form of the resource:  `EPPractitionerUnk`