From Clinical Building Blocks
Jump to: navigation, search


Name: be.en.hd.MedicationPrescription
Version: 0.0.1
Status: Draft


DCM::ContactInformation.Name *
DCM::ContentAuthorList Clinical Building Blocks Expert Group &
DCM::CreationDate 19-12-2013
DCM::DescriptionLanguage en
DCM::Id 2.16.840.1.113883.
DCM::KeywordList Medicatie, Voorschrift
DCM::LifecycleStatus Draft
DCM::ModelerList Clinical Building Blocks Expert Group &
DCM::Name be.en.hd.MedicationPrescription
DCM::ReviewerList Clinical Building Blocks Expert Group &
DCM::RevisionDate 05-01-2016
DCM::Version 0.0.1

Revision History


A medication prescription is an agreement or order for the use of medication in which the following are described: the prescribed product, instructions for use or administration and (optionally) a request for delivery.

The dose information is given for every prescribed product: the start date and time, and if possible stop date and time or total number of administrations, administering schedule (frequency or interval, administering times, link with meals etc.), the number of doses, administering speed or time (for drips), and the route of administration.

An indication can also be included of whether the medication is only to be administered ‘as needed’ and under which conditions the product is to be used, and how high the agreed maximum dose is in a certain period.

If possible, the reason or indication of starting/stopping/changes in use is to be included.

Medication that has been discontinued temporarily can be included as well.

If the prescription also contains the order to provide a product to a patient or to an administerer, it can officially be referred to as a prescription.


The goal of the medication prescription is to provide insight in the therapeutic intention of the healthcare provider in terms of treatment with medicines. Furthermore, it offers the option to record any requests asking the provider of the medication to provide medication to the patient.

Information model

Refer to the legend page for more information about the used types and data types

rootconcept MedicationPrescription
Definition Root concept of the MedicationPrescription building block. This root concept contains all data elements of the MedicationPrescription building block.
Type Zib.png
data MedicationPrescriptionDate
Definition Date on which the prescription was issued.
Datatype TS.png
data ReasonForPrescription::Problem
Definition The medical reason for the prescription or for use of the medication. This can be used to enter a medical indication which was the direct cause for prescription or for use of the medication in question.

It can concern every type of problem (or condition) of the patient, almost always a diagnosis, complaint or symptom.

Please note: The BST401T file of the G standard contains a "special reference" to indicate that "exchange of the reason for prescription is essential".

Datatype Container.png
DCM::ExampleValue Pneumonia due to Streptococcus pneumoniae
DCM::ReferencedDefinitionCode NL-CM:5.1.2 Dit is een verwijzing naar het concept Probleem in de bouwsteen OverdrachtConcern.
container Prescriber
Definition Container of the Prescriber concept. This container contains all data elements of the Prescriber concept.

The person who prescribed the prescription.

Datatype Container.png
context HealthcareProvider
Definition The caregiver responsible for the prescription.
Datatype Verwijzing.png
DCM::ReferencedDefinitionCode NL-CM:17.1.1 Dit is een verwijzing naar het concept Zorgverlener in de bouwsteen Zorgverlener.
context Patient
Definition The patient who prescribed their own product.
Datatype Verwijzing.png
DCM::ReferencedDefinitionCode NL-CM:0.1.1 Dit is een verwijzing naar concept Patiënt in de bouwsteen Patient.
context Caregiver::Contact
Definition The caregiver who prescribed the product.
Datatype Verwijzing.png
DCM::ReferencedDefinitionCode NL-CM:3.1.1 Dit is een verwijzing naar concept Contactpersoon in de bouwsteen Contactpersoon.
data Explanation
Definition Comments on the medication prescription.
Datatype ST.png
data MedicationPrescriptionStatus
Definition The MedicationPrescriptionStatus indicates whether the prescription is actively used, temporarily interrupted, or by now discontinued. The status describes the consecutive stages of the prescription process and is important for the indication of the schedule for use.

Interrupting (home) use often occurs in the event of admittance to a healthcare facility, prior to a procedure and in response to monitoring (level determination, effect measurements, etc.).

When documenting this, the following interpretations are used:  

  • Active: The product is used.
  • Interrupted: Use has (temporarily) been interrupted, because of a surgical procedure, for example. Later, the patient and/or doctor can decide whether or not to resume or discontinue use.
  • Discontinued: There is an assignment or agreement to discontinue use.
  • Completed: The prescription has now been completed (according to the plan, prescription or agreement).
Datatype CD.png
DCM::ExampleValue Actief
DCM::ValueSet File:List.png MedicationPrescriptionStatusCodeList OID: 2.16.840.1.113883.
data MedicationPrescriptionDiscontinuationReason
Definition Reason for discontinuing the use of a certain medicine.
Datatype CD.png
DCM::ValueSet File:List.png MedicationPrescriptionDiscontinuationReasonCodeList OID: 2.16.840.1.113883.
data MedicationPrescriptionInterruptionReason
Definition Reason for interrupting the use of a certain medicine.
Datatype CD.png
DCM::ValueSet File:List.png MedicationPrescriptionInterruptionReasonCodeList OID: 2.16.840.1.113883.


Refer to the legend page for more information about the used types and data types

container Product
Definition Container of the Product concept. This container contains all data elements of the Product concept.

The prescribed product is usually a medicine. However, medical aids and bandages can also be prescribed and supplied via the pharmacy. Strictly speaking, food and blood products do not belong in the medication category, but can be prescribed and supplied by a pharmacy as well.

A type of medication can be indicated with a single code. That code can be chosen from several possible coding systems (concretely: GPK, PRK, HPK or article numbers). Correct use of these codes in the software systems will sufficiently record the composition of the product used, making a complete product specification unnecessary.

In addition to a primary code, alternative codes from other coding systems can also be entered (so that the GPK can be sent along in the event that the patient was registered based on PRK, for example).

Entering multiple ingredients will enable you to display a compound product. If one of the composite parts is liquid, the dosage will be given in milliliters; otherwise it will be given in ‘units’.

In that case, the composition of the medication can be specified implicitly (with the use of a medication code) or explicitly, for example by listing the (active) substance(s) of the medication.

Prescriptions to be prepared by the pharmacy can be entered as well. This can be done by means of the option listed above to enter coded ingredients and/or by entering the composition and preparation method as free text.

Datatype Container.png
container ProductSpecification
Definition Container of the ProductSpecifications concept. This container contains all data elements of the ProductSpecifications concept.

Product specifications are required if the product code is not sufficient to ascertain the active substances and strength.

Datatype Container.png
data ProductName
Definition There is no code for medication entered in free text. In these cases, enter the complete description.
Datatype ST.png
data BrandName
Definition If the ProductCode does not contain a brand name, the brand name can be entered in this concept.
Datatype ST.png
DCM::ExampleValue Lasix
container Ingredient
Definition Container of the Ingredient concept. This container contains all data elements of the Ingredient concept.

A product contains one or more active substances and excipients. These are usually determined by the product code. For medication prepared or compounded by the local pharmacy, each ingredient must be entered separately.

The active substances play an important role, as they:

a) determine the pharmacotherapeutic effect of the medication and

b) serve as the basis for the indication of the strength of the medication (e.g. 200mg).

Datatype Container.png
DCM::ExampleValue captopril
data Concentration
Definition The amount of absorbed active substance or addition per unit of product. This could be a concentration if the medication is dissolved in liquid, for example.
Datatype PQ.png
DCM::ExampleValue 25mg
data ProductCode
Definition Coding medication in the Netherlands is done on the basis of the G standard (issued by Z-index), which is filled under the direction of KNMP.

The coded medication can be expressed as:

  • GTIN International Article Number
  • KNMP article number = ATKODE (2.16.840.1.113883.
  • Trade product code (HPK)
  • Prescription code (PRK)
  • Generic product code (GPK)
  • Anatomic Therapeutic Classification code (ATC)
  • SNOMED CT code
  • 90.000.000 number (individual code setting) (or similar from the facility)

The GTIN enables identification of the product including its origin with a barcode.

The ATKODE is the number with which wholesalers link the article to pharmacy systems (e.g. a box with 3 strips of 10 tablets).

The HPK is the code for the trade product (with the brand name) as used per dose/per time the medication is taken (1 pill, 1 puff, 1ml)

The PRK codes for the same product as the HPK does, but is not linked to a manufacturer (no brand name, no characteristics such as color, geometrical shape etc.). This code will enable a generic prescription, while still defining which trade product can be taken (e.g. a 200ml bag).

The generic product code defines the composition of a product, and is sufficient for recording the prescription, but not the order.

The prescription code (PRK) was developed and added to the older generic (GPK) and supplier-specific (HPK, ATKODE) coding to enable a generic product to be entered without listing a specific brand on the one hand, and to enable providing enough information to support the pharmacy supplying it on the other.

The GTIN coding is used for the implementation of a barcode scanning standard and to be able to trace the origin of the product.

The 90.000.000 number is used in accordance with national agreements.

Datatype CD.png
DCM::ValueSet File:List.png VoorschriftProductATCCodelijst OID: 2.16.840.1.113883.
DCM::ValueSet File:List.png VoorschriftProductGPKCodelijst OID: 2.16.840.1.113883.
DCM::ValueSet File:List.png VoorschriftProductGTINCodelijst OID: 2.16.840.1.113883.
DCM::ValueSet File:List.png VoorschriftProductHPKCodelijst OID: 2.16.840.1.113883.
DCM::ValueSet File:List.png VoorschriftProductPRKCodelijst OID: 2.16.840.1.113883.
DCM::ValueSet File:List.png VoorschriftProductZICodelijst OID: 2.16.840.1.113883.
data Pharmaceutical form
Definition The pharmaceutical form indicates the form of the medication in accordance with the route of administration. Examples include: tablet, suppository, infusion liquid, ointment. If the product has a generic code in the G standard, the form will be known in the G standard. For products without a code (free text, preparation by the pharmacy), the means of administration can be entered.
Datatype CD.png
DCM::ExampleValue 230 (TABLET)
DCM::ValueSet File:List.png FarmaceutischeVormCodelijst OID: 2.16.840.1.113883.
data Substance
Definition Active substance or excipient.

Here, the same codes can be used as for the ProductCode (for dilutions and compounds in particular), but now, the ATC, SSK and SNK codes can also be used to indicate a substance (to list ingredients of local products prepared by the pharmacy).

  • GTIN International Article Number
  • KNMP article number
  • Trade product code (HPK)
  • Prescription code (PRK)
  • Generic product code (GPK)
  • ATC (anatomic therapeutic classification)
  • SSK (substance name code with route of administration)
  • SNK (substance name code)

The ATC is an international classification of pharmaceutical substances without a reference to specific products on the market. Therefore, the ATC code of a generic product will not contain a reference to a certain dose, pharmaceutical form or route of administration; it will only contain a reference to the ingredients (not the amount/concentration/strength).

Datatype CD.png
DCM::ValueSet File:List.png IngredientCodeATCCodelijst OID: 2.16.840.1.113883.
DCM::ValueSet File:List.png IngredientCodeGPKCodelijst OID: 2.16.840.1.113883.
DCM::ValueSet File:List.png IngredientCodeGTINCodelijst OID: 2.16.840.1.113883.
DCM::ValueSet File:List.png IngredientCodeHPKCodelijst OID: 2.16.840.1.113883.
DCM::ValueSet File:List.png IngredientCodePRKCodelijst OID: 2.16.840.1.113883.
DCM::ValueSet File:List.png IngredientCodeSNKCodelijst OID: 2.16.840.1.113883.
DCM::ValueSet File:List.png IngredientCodeSSKCodelijst OID: 2.16.840.1.113883.
DCM::ValueSet File:List.png IngredientCodeZICodelijst OID: 2.16.840.1.113883.


Refer to the legend page for more information about the used types and data types

container Dosage
Definition Container of the Dosage concept. This container contains all data elements of the Dosage concept.

Instructions for the administerer to administer the medication (the patient themselves, a nurse or other aid). When taking stock of medication use, the dosage describes the pattern of use established by the patient.

If the dose schedule (distribution of doses over time) and the dose per administration have been determined, there will be a single instruction for use.

Multiple parallel instructions for use can be included in the event of a changing dose within one day and in the event of a variable frequency of use.

Multiple sequential instructions for use can be included in the event of changing doses within one period and/or in the event of a changing dose schedule.

Datatype Container.png
data StartDate
Definition The date (and time) at which use of the product started or will start according to the dose information.
Datatype TS.png
DCM::ExampleValue 12-03-2012 16:00
data EndDate
Definition The end date of a dose (specification of use). This can be an agreed date, but also the date on which use of the product was discontinued (stop date, discontinuation date).
Datatype TS.png
DCM::ExampleValue 13-10-2012
data DurationOfUse
Definition In some cases, it may be necessary to indicate the intended duration of use, which cannot be calculated from the start date, end date and/or total number of doses. This could for example be the case with temporary sleep medication to be taken as needed.
Datatype PQ.png
DCM::ExampleValue 3 wk
data Number of doses
Definition In many cases, the total number of doses indicates the desired duration of use.
Datatype INT.png
DCM::ExampleValue 1
data Dose
Definition The administration dose indicates the dose amount per administration.

The dosage is described in the unit accompanying the product; usually, this is just a number of units or doses. Liquids and other divisible products will usually include a unit of volume (preferably "ml").

In many cases, the prescriber will want to indicate the dose in units of weight of the active substance.

If only the substance is included and not the product, the amount of that substance will be given. Paracetamol 1000mg is equivalent to 2 Paracetamol 500mg tablets (or units).

The dosage is sometimes given as a calculation, in which the patient’s body weight or body surface area is often used as a parameter. The calculation is however no more than an aid in reaching a decision.

In the event of constant administration, sometimes the dose per administration (e.g. 20ml in a syringe or 500ml in a bag) is given in addition to the administration speed (rate of infusion), but it is often also omitted.

A general dosage recommendation such as ‘Use according to protocol’ or ‘See instructions’ can be sufficient. In that case, no dose per administration is given either.

Datatype PQ.png
DCM::ExampleValue 2; 10ML
data Rate of infusion
Definition The rate of infusion is used in slow administration of liquids. In practice, the measuring unit is almost always ml/hour.

Entering an interval (such as 0-10 ml/hour) is also a commonly used option.

Datatype PQ.png
DCM::ExampleValue 150ml/uur
data DurationOfAdministration
Definition The duration of administration indicates how long the medication is to be administered and used in the event of slow administration of liquids.
Datatype PQ.png
DCM::ExampleValue 120 min
data AdditionalExplanation
Definition The additional explanation contains extra information on the use of or considerations for the current prescription.

This can also include all instructions for use. The text can come from the original "paper" medication prescription, but can also be generated from the coded information.

This concept may contain more information than what is structurally coded in the information below, but may not conflict with it.

The instructions may not conflict with other components of the request for administration.

The instructions can also refer to an existing protocol.

The G standard contains many texts that can support this attribute, in for example G standard table 362, which contains texts from the general practitioners’ standard WCIA table 25. If desired, these texts can be used to structure this concept.

Datatype ST.png
DCM::ExampleValue TIJDENS of vlak NA het eten innemen
data Criterion
Definition The criterion for administering medication can be:


  • a physiological measurement value (plasma glucose concentration, body temperature, blood pressure);
  • a symptom or other circumstance (in the event of a headache, or itch).

Such a criterion will be entered in correspondence with the AsNeeded indicator.

Datatype ST.png
DCM::ExampleValue Plasma glucose > 10 mmol/l.
data Maximum dose
Definition The MaximumAmountPerPeriod concept indicates the maximum duration a product can be used with an 'as needed' prescription.
Datatype PQ.png
DCM::ExampleValue maximaal 4/dag,20/week
data As needed
Definition Indicates whether the dose is only to be administered under certain conditions.
Datatype BL.png
DCM::ExampleValue Ja
container AdministeringSchedule
Definition Container of the AdministeringSchedule concept. This container contains all data elements of the AdministeringSchedule concept.

Specifications of the times at which the medication is administered/is to be administered. This is indicated as follows:

  • Time(s) (16:00) or indications ("before meals") at which the medication is to be taken each day.
  • A specific number of times the medication is to be taken each day ("3x a day"), indicated with the frequency
  • A time interval between consecutive doses ("Every 2 hours", "every 3 days"), indicated with the word Interval.
  • Combined periods with an interval and duration ("1 daily for three out of four weeks: the pill schedule")

If a certain medication is not to be taken daily, the aforementioned can be combined with daily indications:

  • One or more days of the week on which the medication is to be administered (e.g. "Monday, Wednesday, Friday")
  • "3x a week", "2x a month".

The specified administration "infinite" will automatically be repeated until:

  • The end date and time has been reached
  • The total administration duration has been reached (for 14 days)
  • A specific amount of administrations has been reached ("20 doses", "one-time only"), to be entered in the NumberOfDoses concept.
Datatype Container.png
data Frequency
Definition The frequency indicates the number of dose moments per time unit, usually per day. If this frequency is included, then the Interval will not have been included.

In that case, a reasonable distribution throughout the day is expected, but exact times are not given. This is left to the patient. It is the most common type of extramural prescription. In the case of Baxter packs and intramural care, such a prescription is used to draw up a (location-specific) outline for distribution times (logistics).

Datatype PQ.png
DCM::ExampleValue 2x/dag
data Interval
Definition Interval indicates the time between dose times. If this is included, the Frequency will not have been included.

Examples: every 4 hours, every 3 weeks.

The times can now be chosen freely, but distribution throughout the day is more precise, and the interval between times is important (e.g. in the case of antibiotics)

In the case of Baxter packs and intramural care, such a prescription is used to draw up a (location-specific) outline for distribution times (logistics).

Datatype PQ.png
DCM::ExampleValue elke 4 uur
data AdministrationTime
Definition The time of administration is a specific time of day (on the clock). This time usually isn’t (intended to be) exact. There can be multiple administering times in one day.

The intended time of administration can also be entered as a time of day (morning, afternoon, evening, night-time). The administration time is then to be left empty, and the time of day can be entered in the TimeOfDay concept.

Datatype TS.png
DCM::ExampleValue 07:30
data RouteOfAdministration
Definition The route through which the medication is to be administered (oral, nasal, intravenous,...).
Datatype CD.png
DCM::ExampleValue Oraal
DCM::ValueSet File:List.png VoorschriftToedieningswegCodelijst OID: 2.16.840.1.113883.
data DaysOfTheWeek
Definition DaysOfTheWeek indicates a pattern of doses on fixed days of the week.
Datatype CD.png
DCM::ExampleValue maandag
DCM::ValueSet File:List.png WeekdagenCodelijst OID: 2.16.840.1.113883.
data TimeOfDay
Definition To make prescriptions easier for the patient and to facilitate transfers between first and second line, it is best to indicate a time of day instead of a set time.

To code a time of day in the administering schedule, agreements were made between the first and second line to be able to clearly translate the first-line WCIA 21 code to standard times of day in clinical second-line medication assignments. In this process, the following times of day apply:

WCIA Second line

morning 6:00am - 12:00pm

afternoon 12:00pm - 6:00pm

evening 6:00pm - 12:00am

night-time 12:00am - 6:00am

Datatype CD.png
DCM::ValueSet File:List.png DagdeelCodelijst OID: 2.16.840.1.113883.

Supply request

Be.en.hd.MedicationPrescriptionSupply requestModel.png
Refer to the legend page for more information about the used types and data types

container Supply request
Definition Container of the SupplyRequest concept. This container contains all data elements of the SupplyRequest concept.

The supply request is the order placed with the supplier to supply medication. The number of refills can be indicated as well.

Datatype Container.png
data Amount
Definition The amount to be supplied defines the number of units of the ordered product that have to be supplied. The amount is given in the unit of the ordered product. The amount to be supplied is always the amount per partial supply. The number of refills indicates how often this amount is allowed to be supplied.
Datatype PQ.png
DCM::ExampleValue 90 st
data Number of refills
Definition Maximum number of partial supplies (refills) allowed to be given for this prescription.
Datatype INT.png
DCM::ExampleValue 4
context IntendedSupplier::HealthcareProvider
Definition In almost all cases, the intended supplier will be a registered pharmacist.
Datatype Verwijzing.png
DCM::ReferencedDefinitionCode NL-CM:17.1.1 Dit is een verwijzing naar het concept Zorgverlener in de bouwsteen Zorgverlener

Code Lists



Concept Name Concept Code Code System Name Code System OID Description
Active active ActStatus 2.16.840.1.113883.5.14 Actief
Suspended suspended ActStatus 2.16.840.1.113883.5.14 Onderbroken
Aborted aborted ActStatus 2.16.840.1.113883.5.14 Afgebroken
Completed completed ActStatus 2.16.840.1.113883.5.14 Voltooid



Concept Name Concept Code Coding Syst. Name Coding System OID Description
Intolerance SINTOL ActReason 2.16.840.1.113883.5.8 Bijwerking, allergie of intolerantie
Condition alert [Proposed therapy may be inappropriate or contraindicated due to an existing/recent patient condition or diagnosis] COND ActCode 2.16.840.1.113883.5.4 Contra-indicatie [comorbiditeit, diagnose]
Drug interacts with another drug SDDI ActReason 2.16.840.1.113883.5.8 Interactie [interactie met ander medicament met hogere urgentie]
Dose change DOSECHG ActReason 2.16.840.1.113883.5.8 Dosiswijziging
No longer required for treatment NOREQ ActReason 2.16.840.1.113883.5.8 Niet langer vereist voor de behandeling [indicatie vervallen]
Ineffective INEFFECT ActReason 2.16.840.1.113883.5.8 Niet effectief
Formulary policy FP ActReason 2.16.840.1.113883.5.8 Ander voorschrijfbeleid
Product discontinued DISCONT ActReason 2.16.840.1.113883.5.8 Product niet meer leverbaar
Not covered NOTCOVER ActReason 2.16.840.1.113883.5.8 Product wordt niet vergoed
Patient request PAT ActReason 2.16.840.1.113883.5.8 Informatie of wens pati\'ebnt



Concept Name Concept Code Code System Name Code System OID Description
Drug level too high DRUGHIGH ActReason 2.16.840.1.113883.5.8 Te hoge geneesmiddel spiegel
Lab interference issues LABINT ActReason 2.16.840.1.113883.5.8 Interferentie met gepland labonderzoek
Parent is pregnant/breast feeding PREG ActReason 2.16.840.1.113883.5.8 Zwangerschap of borstvoeding
Patient not-available NON-AVAIL ActReason 2.16.840.1.113883.5.8 Pati\'ebnt is tijdelijk afwezig of ondergaat ingreep
Response to monitoring MONIT ActReason 2.16.840.1.113883.5.8 Reactie op monitoring
Drug interacts with another drug SDDI ActReason 2.16.840.1.113883.5.8 Interactie met ander medicament met hogere urgentie
Duplicate therapy SDUPTHER ActReason 2.16.840.1.113883.5.8 Een andere therapie maakt het gebruik tijdelijk overbodig
Patient scheduled for surgery SURG ActReason 2.16.840.1.113883.5.8 Geplande ingreep
Waiting for old drug to wash out WASHOUT ActReason 2.16.840.1.113883.5.8 Tijdelijk onderbreken tot ander geneesmiddel geen werking meer uitoefent



Codes Coding Syst. Name Coding System OID
Alle waarden Anatomic Therapeutic Classification (ATC) 2.16.840.1.113883.6.73



Codes Coding Syst. Name Coding System OID
105904009 SNOMED 2.16.840.1.113883.



Codes Coding Syst. Name Coding System OID
Alle waarden Anatomic Therapeutic Classification (ATC) 2.16.840.1.113883.6.73



Codes Coding Syst. Name Coding System OID
SNOMED CT: <284009009 SNOMED CT 2.16.840.1.113883.6.96



Concept Name Concept Code Code System Name Code System OID Description
Monday 307145004 SNOMED CT 2.16.840.1.113883.6.96 maandag
Tuesday 307147007 SNOMED CT 2.16.840.1.113883.6.96 dinsdag
Wednesday 307148002 SNOMED CT 2.16.840.1.113883.6.96 woensdag
Thursday 307149005 SNOMED CT 2.16.840.1.113883.6.96 donderdag
Friday 307150005 SNOMED CT 2.16.840.1.113883.6.96 vrijdag
Saturday 307151009 SNOMED CT 2.16.840.1.113883.6.96 zaterdag
Sunday 307146003 SNOMED CT 2.16.840.1.113883.6.96 zondag



Concept Name Concept Code Coding Syst. Name Coding System OID Description
During the morning 73775008 SNOMED CT 2.16.840.1.113883.6.96 's ochtends
During the afternoon 255213009 SNOMED CT 2.16.840.1.113883.6.96 's middags
During the evening 3157002 SNOMED CT 2.16.840.1.113883.6.96 's avonds
During the night 2546009 SNOMED CT 2.16.840.1.113883.6.96 's nachts


1. GROOT, E. (2011) Dataset medicatieproces 2011. [Online] Den Haag: Nictiz. Beschikbaar op: [Geraadpleegd: 23 juli 2014].

2. HL7v3-implementatiehandleiding medicatieproces versie [Online] Den Haag: Nictiz. Beschikbaar op: [Geraadpleegd: 23 juli 2014].

3. Dossier Medicatieoverzicht. [Online] Beschikbaar op: [Geraadpleegd: 23 juli 2014].

4. G-standaard documentatie. [Online] Beschikbaar op: [Geraadpleegd: 23 juli 2014].