InstructionsForUse-v1.1(2017EN): verschil tussen versies

Uit Zorginformatiebouwstenen
Naar navigatie springen Naar zoeken springen
(Nieuwe pagina aangemaakt met '==General information== Name: '''nl.zorg.part.InstructionsForUse''' link=GebruiksInstructie-v1.1(2017NL)<BR> Version: '''1.1''' <br> HCIM Stat...')
 
Geen bewerkingssamenvatting
 
(3 tussenliggende versies door dezelfde gebruiker niet weergegeven)
Regel 1: Regel 1:
==General information==
<!-- Hieronder wordt een transclude page aangeroepen -->
Name: '''nl.zorg.part.InstructionsForUse''' [[Bestand:NL.png|link=GebruiksInstructie-v1.1(2017NL)]]<BR>
{{Versions-2.16.840.1.113883.2.4.3.11.60.40.3.9.12(EN)|1|InstructionsForUse-v1.1(2017EN)}}
Version: '''1.1''' <br>
<!-- Tot hier de transclude page -->
HCIM Status:Final<br>
==General information<!--hdGeneralInformation-->==
Release: '''2017''' <br>
Name<!--hdName-->: '''nl.zorg.part.InstructionsForUse''' [[Bestand:NL.png|link=GebruiksInstructie-v1.1(2017NL)]]<BR>
Release status: Published<br>
Version<!--hdVersion-->: '''1.1''' <br>
Release date: 31-12-2017
HCIM Status<!--hdStatus-->:Final<br>
Release<!--hdPublication-->: '''2017''' <br>
Release status<!--hdPublicationStatus-->: Published<br>
Release date<!--hdPublicationDate-->: 31-12-2017
-----
-----
<div style="text-align: right; direction: ltr; margin-left: 1em;" >[[Bestand: Back 16.png| link= HCIM_Release_2017(EN)]] [[HCIM_Release_2017(EN) |Back to HCIM list ]]</div>
<div style="text-align: right; direction: ltr; margin-left: 1em;" >[[Bestand: Back 16.png| link= HCIM_Release<!--wikiReleasePage-->_2017(EN)]] [[HCIM_Release<!--wikiReleasePage-->_2017(EN) |Back to HCIM list<!--hdBackToMainPage--> ]]</div>


==Metadata==
==Metadata==
Regel 61: Regel 64:
==Revision History==
==Revision History==
<div class="mw-collapsible mw-collapsed">
<div class="mw-collapsible mw-collapsed">
''Only available in Dutch''
''Only available in Dutch<!--noTranslation-->''


<u>Publicatieversie 1.0</u> (04-09-2017)
<u>Publicatieversie 1.0</u> (04-09-2017)
Regel 69: Regel 72:
|-
|-
|style="width:75px; "|[[ZIBIssues#ZIB-617 | ZIB-617 ]]
|style="width:75px; "|[[ZIBIssues#ZIB-617 | ZIB-617 ]]
|Geen informatie
|Toevoeging aan Eenheid van Keerdosis
|-
|-
|style="width:75px; "|[[ZIBIssues#ZIB-643 | ZIB-643 ]]
|style="width:75px; "|[[ZIBIssues#ZIB-643 | ZIB-643 ]]
|Geen informatie
|Kleine tekstuele verbeteringen
|}
|}
</div>
</div>
Regel 85: Regel 88:
==Information Model==
==Information Model==
<BR>
<BR>
<imagemap> Bestand:InstructionsForUse-v1.1Model(EN).png | center  
<imagemap> Bestand:InstructionsForUse-v1.1Model(2017EN).png | center  
rect 37 805 193 855 [[#AsNeededCriteriumCodelist]]
rect 47 813 203 863 [[#AsNeededCriteriumCodelist]]
rect 534 90 734 150 [[#RouteOfAdministrationCodelist]]
rect 544 98 744 158 [[#RouteOfAdministrationCodelist]]
rect 636 805 748 865 [[#TimeOfDayCodelist]]
rect 646 813 758 873 [[#TimeOfDayCodelist]]
rect 486 805 615 865 [[#WeekDayCodelist]]
rect 496 813 625 873 [[#WeekDayCodelist]]
rect 212 714 312 784 [[#13202]]
rect 222 722 322 792 [[#13202]]
rect 75 714 165 784 [[#13221]]
rect 85 722 175 792 [[#13221]]
rect 641 714 731 784 [[#13205]]
rect 651 722 741 792 [[#13205]]
rect 503 713 593 783 [[#13213]]
rect 513 721 603 791 [[#13213]]
rect 641 573 731 643 [[#13208]]
rect 651 581 741 651 [[#13208]]
rect 641 451 731 521 [[#13207]]
rect 651 459 741 529 [[#13207]]
rect 373 713 463 783 [[Range-v1.0(2017EN)]]
rect 383 721 473 791 [[Range-v1.0(2017EN)]]
rect 313 573 421 643 [[Range-v1.0(2017EN)]]
rect 323 581 431 651 [[Range-v1.0(2017EN)]]
rect 487 573 593 643 [[#13209]]
rect 497 581 603 651 [[#13209]]
rect 149 573 239 643 [[#13217]]
rect 159 581 249 651 [[#13217]]
rect 485 432 594 502 [[Range-v1.0(2017EN)]]
rect 495 440 604 510 [[Range-v1.0(2017EN)]]
rect 149 432 239 502 [[Range-v1.0(2017EN)]]
rect 159 440 249 510 [[Range-v1.0(2017EN)]]
rect 313 432 421 502 [[#13203]]
rect 323 440 431 510 [[#13203]]
rect 149 310 239 380 [[#13214]]
rect 159 318 249 388 [[#13214]]
rect 495 310 585 380 [[#13215]]
rect 505 318 595 388 [[#13215]]
rect 313 310 421 380 [[#13206]]
rect 323 318 431 388 [[#13206]]
rect 73 196 238 266 [[#13218]]
rect 83 204 248 274 [[#13218]]
rect 372 85 488 155 [[#13220]]
rect 382 93 498 163 [[#13220]]
rect 495 198 585 268 [[#13222]]
rect 505 206 595 276 [[#13222]]
rect 229 85 319 155 [[#13225]]
rect 239 93 329 163 [[#13225]]
rect 313 198 421 268 [[#13226]]
rect 323 206 431 276 [[#13226]]
desc none
desc none
</imagemap>
</imagemap>
Regel 116: Regel 119:
{| border= "1"  width="1500px" style = "font-size: 9.5pt;  border: solid 1px silver; border-collapse:collapse;" cellpadding = "3px" cellspacing ="0px"  
{| border= "1"  width="1500px" style = "font-size: 9.5pt;  border: solid 1px silver; border-collapse:collapse;" cellpadding = "3px" cellspacing ="0px"  
|-style="background-color: #1F497D; color: white; font-weight: bold; font-variant: small-caps; "
|-style="background-color: #1F497D; color: white; font-weight: bold; font-variant: small-caps; "
|style="width:30px;"|Type||style="width:100px;"|Id||colspan="6 " style="width:140px;"|Concept||Card.||style="width: 600px;"|Definition||style="width:200px;"|DefinitionCode||style="width:200px;"|Reference
|style="width:30px;"|Type<!--imType-->||style="width:100px;"|Id<!--imId-->||colspan="6 " style="width:140px;"|Concept<!--imConcept-->||Card.<!--imCard-->||style="width: 600px;"|Definition<!--imDefinition-->||style="width:200px;"|DefinitionCode<!--imDefinitionCode-->||style="width:200px;"|Reference<!--imReference-->
|-style="vertical-align:top; background-color: #E3E3E3; "
|-style="vertical-align:top; background-color: #E3E3E3; "
|style = "text-align:center" |[[Bestand: block.png| 20px | link=]]
|style = "text-align:center" |[[Bestand: block.png| 20px | link=]]
Regel 472: Regel 475:
|
|
|}
|}
Columns Concept and DefinitionCode: hover over the values for more information<BR>
Columns Concept and DefinitionCode: hover over the values for more information<!--imHover--><BR>
For explanation of the symbols, please see the legend page [[Bestand:list2.png|link=Legend]]
For explanation of the symbols, please see the legend page<!--imLegend--> [[Bestand:list2.png|link=Legend<!--wikiLegend-->]]


==Example Instances==
==Example Instances==
''Only available in Dutch''
''Only available in Dutch<!--noTranslation-->''


{|class="wikitable" width="930px" style= "font-size: 9.5pt;"
{|class="wikitable" width="930px" style= "font-size: 9.5pt;"
Regel 510: Regel 513:
{| class="wikitable" width="60%"  
{| class="wikitable" width="60%"  
|-style='vertical-align:top; background-color: #E8D7BE;'
|-style='vertical-align:top; background-color: #E8D7BE;'
|Valueset OID 2.16.840.1.113883.2.4.3.11.60.40.2.9.12.4
|Valueset OID<!--vsValuesetOID-->: 2.16.840.1.113883.2.4.3.11.60.40.2.9.12.4
|Binding<!--vsBindingTag-->:
|}
|}
{| class="wikitable"  width="60% "
{| class="wikitable"  width="60% "
|-style="background-color: #1F497D; color: white; font-weight: bold; "
|-style="background-color: #1F497D; color: white; font-weight: bold; "
|Conceptname
|Conceptname<!--vsConceptName-->
|Conceptcode
|Conceptcode<!--vsConceptCode-->
|Codesystem name||Codesystem OID
|Codesystem name<!--vsConceptSystemName-->||Codesystem OID<!--vsConceptSystemOID-->
|Description
|Description<!--vsDescription-->
|-style="vertical-align:top; "
|-style="vertical-align:top; "
|Bij een aanval
|Bij een aanval
Regel 597: Regel 601:
|Geen Informatie
|Geen Informatie
|}
|}
=== RouteOfAdministrationCodelist===
=== RouteOfAdministrationCodelist===
{| class="wikitable" width="60%"  
{| class="wikitable" width="60%"  
|-style='vertical-align:top; background-color: #E8D7BE;'
|-style='vertical-align:top; background-color: #E8D7BE;'
|Valueset OID 2.16.840.1.113883.2.4.3.11.60.40.2.9.12.1
|Valueset OID<!--vsValuesetOID-->: 2.16.840.1.113883.2.4.3.11.60.40.2.9.12.1
|Binding<!--vsBindingTag-->:
|}
|}
{| class="wikitable"  width="60% "
{| class="wikitable"  width="60% "
|-style="background-color: #1F497D; color: white; font-weight: bold; "
|-style="background-color: #1F497D; color: white; font-weight: bold; "
|Conceptname
|Conceptname<!--vsConceptName-->
|Codesystem name||Codesystem OID
|Codesystem name<!--vsConceptSystemName-->||Codesystem OID<!--vsConceptSystemOID-->
|-style="vertical-align:top; "
|-style="vertical-align:top; "
|Alle waarden
|Alle waarden
Regel 612: Regel 616:
|2.16.840.1.113883.2.4.4.9
|2.16.840.1.113883.2.4.4.9
|}
|}
=== TimeOfDayCodelist===
=== TimeOfDayCodelist===
{| class="wikitable" width="60%"  
{| class="wikitable" width="60%"  
|-style='vertical-align:top; background-color: #E8D7BE;'
|-style='vertical-align:top; background-color: #E8D7BE;'
|Valueset OID 2.16.840.1.113883.2.4.3.11.60.40.2.9.12.3
|Valueset OID<!--vsValuesetOID-->: 2.16.840.1.113883.2.4.3.11.60.40.2.9.12.3
|Binding<!--vsBindingTag-->:
|}
|}
{| class="wikitable"  width="60% "
{| class="wikitable"  width="60% "
|-style="background-color: #1F497D; color: white; font-weight: bold; "
|-style="background-color: #1F497D; color: white; font-weight: bold; "
|Conceptname
|Conceptname<!--vsConceptName-->
|Conceptcode
|Conceptcode<!--vsConceptCode-->
|Codesystem name||Codesystem OID
|Codesystem name<!--vsConceptSystemName-->||Codesystem OID<!--vsConceptSystemOID-->
|Description
|Description<!--vsDescription-->
|-style="vertical-align:top; "
|-style="vertical-align:top; "
|During the morning
|During the morning
|73775008
|[https://terminologie.nictiz.nl/art-decor/snomed-ct?conceptId=73775008 73775008]
|SNOMED CT
|SNOMED CT
|2.16.840.1.113883.6.96
|2.16.840.1.113883.6.96
Regel 632: Regel 636:
|-style="vertical-align:top; "
|-style="vertical-align:top; "
|During the afternoon
|During the afternoon
|255213009
|[https://terminologie.nictiz.nl/art-decor/snomed-ct?conceptId=255213009 255213009]
|SNOMED CT
|SNOMED CT
|2.16.840.1.113883.6.96
|2.16.840.1.113883.6.96
Regel 638: Regel 642:
|-style="vertical-align:top; "
|-style="vertical-align:top; "
|During the evening
|During the evening
|3157002
|[https://terminologie.nictiz.nl/art-decor/snomed-ct?conceptId=3157002 3157002]
|SNOMED CT
|SNOMED CT
|2.16.840.1.113883.6.96
|2.16.840.1.113883.6.96
Regel 644: Regel 648:
|-style="vertical-align:top; "
|-style="vertical-align:top; "
|During the night
|During the night
|2546009
|[https://terminologie.nictiz.nl/art-decor/snomed-ct?conceptId=2546009 2546009]
|SNOMED CT
|SNOMED CT
|2.16.840.1.113883.6.96
|2.16.840.1.113883.6.96
|''s nachts
|''s nachts
|}
|}
=== WeekDayCodelist===
=== WeekDayCodelist===
{| class="wikitable" width="60%"  
{| class="wikitable" width="60%"  
|-style='vertical-align:top; background-color: #E8D7BE;'
|-style='vertical-align:top; background-color: #E8D7BE;'
|Valueset OID 2.16.840.1.113883.2.4.3.11.60.40.2.9.12.2
|Valueset OID<!--vsValuesetOID-->: 2.16.840.1.113883.2.4.3.11.60.40.2.9.12.2
|Binding<!--vsBindingTag-->:
|}
|}
{| class="wikitable"  width="60% "
{| class="wikitable"  width="60% "
|-style="background-color: #1F497D; color: white; font-weight: bold; "
|-style="background-color: #1F497D; color: white; font-weight: bold; "
|Conceptname
|Conceptname<!--vsConceptName-->
|Conceptcode
|Conceptcode<!--vsConceptCode-->
|Codesystem name||Codesystem OID
|Codesystem name<!--vsConceptSystemName-->||Codesystem OID<!--vsConceptSystemOID-->
|Description
|Description<!--vsDescription-->
|-style="vertical-align:top; "
|-style="vertical-align:top; "
|Monday
|Monday
|307145004
|[https://terminologie.nictiz.nl/art-decor/snomed-ct?conceptId=307145004 307145004]
|SNOMED CT
|SNOMED CT
|2.16.840.1.113883.6.96
|2.16.840.1.113883.6.96
Regel 669: Regel 673:
|-style="vertical-align:top; "
|-style="vertical-align:top; "
|Tuesday
|Tuesday
|307147007
|[https://terminologie.nictiz.nl/art-decor/snomed-ct?conceptId=307147007 307147007]
|SNOMED CT
|SNOMED CT
|2.16.840.1.113883.6.96
|2.16.840.1.113883.6.96
Regel 675: Regel 679:
|-style="vertical-align:top; "
|-style="vertical-align:top; "
|Wednesday
|Wednesday
|307148002
|[https://terminologie.nictiz.nl/art-decor/snomed-ct?conceptId=307148002 307148002]
|SNOMED CT
|SNOMED CT
|2.16.840.1.113883.6.96
|2.16.840.1.113883.6.96
Regel 681: Regel 685:
|-style="vertical-align:top; "
|-style="vertical-align:top; "
|Thursday
|Thursday
|307149005
|[https://terminologie.nictiz.nl/art-decor/snomed-ct?conceptId=307149005 307149005]
|SNOMED CT
|SNOMED CT
|2.16.840.1.113883.6.96
|2.16.840.1.113883.6.96
Regel 687: Regel 691:
|-style="vertical-align:top; "
|-style="vertical-align:top; "
|Friday
|Friday
|307150005
|[https://terminologie.nictiz.nl/art-decor/snomed-ct?conceptId=307150005 307150005]
|SNOMED CT
|SNOMED CT
|2.16.840.1.113883.6.96
|2.16.840.1.113883.6.96
Regel 693: Regel 697:
|-style="vertical-align:top; "
|-style="vertical-align:top; "
|Saturday
|Saturday
|307151009
|[https://terminologie.nictiz.nl/art-decor/snomed-ct?conceptId=307151009 307151009]
|SNOMED CT
|SNOMED CT
|2.16.840.1.113883.6.96
|2.16.840.1.113883.6.96
Regel 699: Regel 703:
|-style="vertical-align:top; "
|-style="vertical-align:top; "
|Sunday
|Sunday
|307146003
|[https://terminologie.nictiz.nl/art-decor/snomed-ct?conceptId=307146003 307146003]
|SNOMED CT
|SNOMED CT
|2.16.840.1.113883.6.96
|2.16.840.1.113883.6.96
Regel 705: Regel 709:
|}
|}


 
==This information model in other releases<!--ftOtherReleases-->==
==This information model in other releases==
<!-- Hieronder wordt een transclude page aangeroepen -->
---
{{Versions-2.16.840.1.113883.2.4.3.11.60.40.3.9.12(EN)|2|2017}}
==More on this information model==
<!-- Tot hier de transclude page -->
==Information model references<!--ftReferences-->==
====This information model refers to<!--ftRefersTo-->====
*[[Range-v1.0(2017EN)|Range-v1.0]]
====This information model is used in<!--ftReferredBy-->====
*[[AdministrationAgreement-v1.0.1(2017EN)|AdministrationAgreement-v1.0.1]]
*[[MedicationAgreement-v1.0.1(2017EN)|MedicationAgreement-v1.0.1]]
*[[MedicationUse2-v1.0.1(2017EN)|MedicationUse2-v1.0.1]]
==Technical specifications in HL7v3 CDA and HL7 FHIR<!--ftHeader-->==
To exchange information based on health and care information models, additional, more technical specifications are required.<BR>
To exchange information based on health and care information models, additional, more technical specifications are required.<BR>
Not every environment can handle the same technical specifications. For this reason, there are several types of technical specifications:
Not every environment can handle the same technical specifications. For this reason, there are several types of technical specifications:<!--ftReferenceIntro-->
<ul>
<ul>
<li>HL7® version 3 CDA compatible specifications, available through the Nictiz ART-DECOR® environment [http://decor.nictiz.nl/art-decor/decor-scenarios--zib2017bbr-?id=2.16.840.1.113883.2.4.3.11.60.7.4.2.9.12&effectiveDate=2017-12-31T00:00:00&language=en-US&scenariotree=false [[File:artdecor.jpg|16px|link=]]]</li>
<li>HL7® version 3 CDA compatible specifications, available through the Nictiz ART-DECOR® environment<!--ftArtDecorReference--> [http://decor.nictiz.nl/art-decor/decor-scenarios--zib2017bbr-?id=2.16.840.1.113883.2.4.3.11.60.7.4.2.9.12&effectiveDate=2017-12-31T00:00:00&language=en-US&scenariotree=false [[File:artdecor.jpg|16px|link=]]]</li>
<li>HL7® FHIR® compatible specifications, available through the Nictiz environment on the Simplifier FHIR [https://simplifier.net/NictizSTU3/~resources?text=zib&category=StructureDefinition [[File:fhir.png|link=]]]</li>
<li>HL7® FHIR® compatible specifications, available through the Nictiz environment on the Simplifier FHIR<!--ftSimplifierReference--> {{SimplefierLinks|2017}}</li>
</ul>
</ul>
This information model is also available as [[Media:nl.zorg.part.InstructionsForUse-v1.1(2017EN).pdf|pdf file]] [[File:PDF.png|link=]] or as [[Media:nl.zorg.part.InstructionsForUse-v1.1(2017EN).xlsx|spreadsheet]] [[File:xlsx.png|link=]]
==Downloads<!--ftDownloadTitle-->==
==About this information==
This information model is also available as [[Media:nl.zorg.part.InstructionsForUse-v1.1(2017EN).pdf|pdf file]] [[File:PDF.png|link=]] or as [[Media:nl.zorg.part.InstructionsForUse-v1.1(2017EN).xlsx|spreadsheet]] [[File:xlsx.png|link=]]<!--ftDownloads-->
The information in this wikipage is based on Release 2017 <BR>
==About this information<!--ftHeader2-->==
Conditions for use are located on the mainpage [[Bestand:list2.png|link=HCIM_Mainpage]]<BR>
The information in this wikipage is based on<!--ftInfoBase--> Release 2017 <BR>
This page is generated on 22/01/2018 00:24:49 <BR>
Conditions for use are located on the mainpage<!--ftConditions--> [[Bestand:list2.png|link=HCIM_Mainpage<!--wikiMainpage-->]]<BR>
This page is generated on 21/12/2018 14:05:53 with ZibExtraction v. 3.0.6929.24609<!--ftDate--> <BR>
-----
-----
<div style="text-align: right; direction: ltr; margin-left: 1em;" >[[Bestand: Back 16.png| link= HCIM_Release_2017(EN)]] [[HCIM_Release_2017(EN) |Back to HCIM list ]]</div>
<div style="text-align: right; direction: ltr; margin-left: 1em;" >[[Bestand: Back 16.png| link= HCIM_Release<!--wikiReleasePage-->_2017(EN)]] [[HCIM_Release<!--wikiReleasePage-->_2017(EN) |Back to HCIM list<!--hdBackToMainPage--> ]]</div>

Huidige versie van 24 dec 2018 om 12:03


Attention!! This is not the most recent version of this information model. You can find the most recent version ''here''.

General information

Name: nl.zorg.part.InstructionsForUse NL.png
Version: 1.1
HCIM Status:Final
Release: 2017
Release status: Published
Release date: 31-12-2017


Back 16.png Back to HCIM list

Metadata

DCM::CoderList Projectgroep Medicatieproces
DCM::ContactInformation.Address
DCM::ContactInformation.Name
DCM::ContactInformation.Telecom
DCM::ContentAuthorList Projectgroep Medicatieproces
DCM::CreationDate 1-3-2017
DCM::DeprecatedDate
DCM::DescriptionLanguage nl
DCM::EndorsingAuthority.Address
DCM::EndorsingAuthority.Name
DCM::EndorsingAuthority.Telecom
DCM::Id 2.16.840.1.113883.2.4.3.11.60.40.3.9.12
DCM::KeywordList
DCM::LifecycleStatus Final
DCM::ModelerList
DCM::Name nl.zorg.part.GebruiksInstructie
DCM::PublicationDate 31-12-2017
DCM::PublicationStatus Published
DCM::ReviewerList Projectgroep Medicatieproces & Architectuurgroep Registratie aan de Bron
DCM::RevisionDate 31-12-2017
DCM::Superseeds nl.zorg.part.GebruiksInstructie-v1.0
DCM::Version 1.1
HCIM::PublicationLanguage EN

Revision History

Only available in Dutch

Publicatieversie 1.0 (04-09-2017)

Publicatieversie 1.1 (31-12-2017)

ZIB-617 Toevoeging aan Eenheid van Keerdosis
ZIB-643 Kleine tekstuele verbeteringen

Concept

Instructions for the use or administration of the medication, e.g. dose and route of administration. In the event of medication use, this is the pattern of use established by the patient or which the patient followed.
This is a partial information model

Purpose

InstructionsForUse gives an insight into the manner a drug is to be used.

Information Model


#AsNeededCriteriumCodelist#RouteOfAdministrationCodelist#TimeOfDayCodelist#WeekDayCodelist#13202#13221#13205#13213#13208#13207Range-v1.0(2017EN)Range-v1.0(2017EN)#13209#13217Range-v1.0(2017EN)Range-v1.0(2017EN)#13203#13214#13215#13206#13218#13220#13222#13225#13226InstructionsForUse-v1.1Model(2017EN).png


Type Id Concept Card. Definition DefinitionCode Reference
Block.png NL-CM:9.12.22504 Arrowdown.pngInstructionsForUse Root concept of the InstructionsForUse partial information model. This root concept contains all data elements of the InstructionsForUse partial information model.
ST.png NL-CM:9.12.19944 Arrowright.pngAdditionalInstructions 0..* The additional instructions contain 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.

ST.png NL-CM:9.12.9581 Arrowright.pngDescription 0..1 Textual description of the complete instructions for use including the period of use.
PQ.png NL-CM:9.12.22505 Arrowright.pngRepeatPeriodCyclicalSchedule 0..1 The repeated period in a cyclical schedule (of one or more dosing instructions). A cyclic schedule is noted in days, the corresponding dosing duration is also in days.

Examples of a cyclical schedule: contraceptive pill (21 days, 1 pill 1x a day, then skip for 7 days, repeat), repeat period here is 28 days

CD.png NL-CM:9.12.19941 Arrowright.pngRouteOfAdministration 0..1 The route through which the medication is administered (oral, nasal, intravenous, etc.).
List2.png RouteOfAdministrationCodelist
Folder.png NL-CM:9.12.22095 Arrowdown.pngDosingInstructions 0..* Dosing instructions
PQ.png NL-CM:9.12.22506 Arrowright.pngDoseDuration 0..1 The intended time duration for these dosing instructions, e.g. 5 days or 8 weeks.

In the case of medication for an indefinite period, the dosing duration is left empty in the last dosing instruction. Leaving dose duration empty should only be used for medication for an indefinite period.

INT.png NL-CM:9.12.22503 Arrowright.pngSequenceNumber 0..1 This indicates the sequence of the dosing instructions within the medication agreement.
Folder.png NL-CM:9.12.19935 Arrowdown.pngDosage 0..* Container of the Dosage concept. This container contains all data elements of the Dosage concept.

Instructions for the administrator 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.

Once the dose schedule (distribution of doses over time) and the dose have been determined, then there should be one 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 use frequency.

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.

Verwijzing.png NL-CM:9.12.19942 Arrowright.pngAdministeringSpeed::Range 0..1 The administering speed is used in slow administration of liquid. 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.

For example, with an administering speed of 10ml/hour:

  • amount = 10,
  • dose unit = ml,
  • time unit = hour

Optionally a translation to NHG table Gebruiksvoorschriften(Table 25) is also allowed.

Block.png Range
Verwijzing.png NL-CM:9.12.23141 Arrowright.pngDurationOfAdministration 0..1 The duration of administration defines the length of time during which the drug is administered and is mainly used in the slow parenteral administration of fluids.Optionally a translation to NHG table Gebruiksvoorschriften(Table 25) is also allowed.
Block.png Range
Verwijzing.png NL-CM:9.12.19940 Arrowright.pngDose::Range 0..1 The 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 ingredient.

If only the ingredient is included and not the product, then the amount of that ingredient 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 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 is given in addition to the administration speed (infusion rate) (e.g. 20ml in a syringe or 500ml in a bag), 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 is given.

Optionally a translation to NHG table Gebruiksvoorschriften(Table 25) is also allowed.

Block.png Range
Folder.png NL-CM:9.12.22512 Arrowdown.pngAsNeeded 0..1 As needed means that the dose is only to be administered under certain conditions.

See also the Instructions section for more information about use of the element.

CD.png NL-CM:9.12.19945 Arrowright.pngCondition 0..1 The condition 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).

Relevant B codes in Table 25 make up the list of values for coded entering of this concept. Also always include the textual description of that code. Physiological measurement values or other conditions that do not occur in the B codes in Tabel25 do not need to be coded. These can be expressed in free text in the Description concept.

List2.png AsNeededCriteriumCodelist
PQ.png NL-CM:9.12.19946 Arrowright.pngMaximumDose 0..1 A maximum dose indicates the maximum duration a product can be used with an ‘as needed’ prescription.

Optionally a translation to NHG table Gebruiksvoorschriften(Table 25) is also allowed.

Folder.png NL-CM:9.12.19948 Arrowdown.pngAdministeringSchedule 0..1 Specifications of the times at which the medication 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 week days on which the medication is to be administered (e.g. “Monday, Wednesday, Friday”)
  • ”3x a week”, “2x a month”.

The specified administration “infinite” is automatically to be repeated until:

  • The end date and time has been reached
  • The total administration duration has been reached (14 days)
  • A specific amount of administrations has been reached (“20 doses”), to be entered in the Frequency concept.
Verwijzing.png NL-CM:9.12.19949 Arrowright.pngFrequency::Range 0..1 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. Usually, frequency comprises both amount and time unit (3 times a day), but it can occur without the time unit (single use).

In that case, a reasonable distribution over the day is expected, but exact times are not given. This is left to the patient. It is the most common manner 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).

The time unit of the frequency must be the same as how it is indicated in the textual description of the dose.

Example: for a '2x a day...' dose:

  • amount = 2
  • time unit = 'day'.

for a '3x a week...' dose:

  • amount = 3
  • time unit = 'week'.

Optionally a translation to NHG table Gebruiksvoorschriften(Table 25) is also allowed.

Block.png Range
CD.png NL-CM:9.12.19952 Arrowright.pngWeekDay 0..* WeekDay indicates a pattern of doses on fixed week days.
List2.png WeekDayCodelist
CD.png NL-CM:9.12.19953 Arrowright.pngTimeOfDay 0..* Time of day: morning, afternoon, evening, night.
List2.png TimeOfDayCodelist
TS.png NL-CM:9.12.19951 Arrowright.pngAdministrationTime 0..* 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 ideal 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.

PQ.png NL-CM:9.12.19950 Arrowright.pngInterval 0..1 Interval indicates the time between dose times. If this is included, then 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).

Columns Concept and DefinitionCode: hover over the values for more information
For explanation of the symbols, please see the legend page List2.png

Example Instances

Only available in Dutch

Gebruiksinstructie
Omschrijving Doseerinstructie
Doseerduur Dosering|Keerdosis Toedieningsschema |Frequentie |Interval |Toedientijd |Weekdag |Dagdeel
Van 8-9-2017 tot 18-9-2017 1x per dag 1 stuk. Vanaf 18-9-2017 staken. 1 stuk 1x per dag
Vanaf 6 maart 2016 1x per week op maandag om 14uur 15 mg (=0,6 ml) 15 mg (=0,6 ml) 1x per week op maandag (14u)

Instructions

AsNeeded dosage:
Using the term 'as needed' or a specific reason (eg 'in case of pain') to use medication leads to ambiguity. It is not always clear whether the whole dose is 'as needed' or only part of the dose. For example: 1x daily 1-2 tablets as needed. This can mean: 1 tablet fixed per day and 1 tablet as needed or, as needed, a maximum of 2 tablets.As needed medication is not included in GDS. In the first situation, 1 tablet comes in the GDS (drug dispensing systems) and 1 tablet is delivered separately. In the second situation there is only separate delivery.The system must make sufficiently clear whether the entire instruction or part of the dose is necessary. The ZIB supports both options described above.

Valuesets

AsNeededCriteriumCodelist

Valueset OID: 2.16.840.1.113883.2.4.3.11.60.40.2.9.12.4 Binding:
Conceptname Conceptcode Codesystem name Codesystem OID Description
Bij een aanval 1022 WCIAv3 Tabel 25 B-codes 2.16.840.1.113883.2.4.4.5 Bij een aanval
Bij benauwdheid 1023 WCIAv3 Tabel 25 B-codes 2.16.840.1.113883.2.4.4.5 Bij benauwdheid
Bij diarree 1024 WCIAv3 Tabel 25 B-codes 2.16.840.1.113883.2.4.4.5 Bij diarree
Bij pijn 1028 WCIAv3 Tabel 25 B-codes 2.16.840.1.113883.2.4.4.5 Bij pijn
Bij jeuk 1121 WCIAv3 Tabel 25 B-codes 2.16.840.1.113883.2.4.4.5 Bij jeuk
Zo nodig 1137 WCIAv3 Tabel 25 B-codes 2.16.840.1.113883.2.4.4.5 Zo nodig
Bij hoofdpijn 1144 WCIAv3 Tabel 25 B-codes 2.16.840.1.113883.2.4.4.5 Bij hoofdpijn
Bij koorts 1145 WCIAv3 Tabel 25 B-codes 2.16.840.1.113883.2.4.4.5 Bij koorts
Bij hoge koorts 1146 WCIAv3 Tabel 25 B-codes 2.16.840.1.113883.2.4.4.5 Bij hoge koorts
Bij koorts en/of pijn 1147 WCIAv3 Tabel 25 B-codes 2.16.840.1.113883.2.4.4.5 Bij koorts en/of pijn
Bij hoest 1387 WCIAv3 Tabel 25 B-codes 2.16.840.1.113883.2.4.4.5 Bij hoest
Overig OTH NullFlavor 2.16.840.1.113883.5.1008 Overig
Geen Informatie NI NullFlavor 2.16.840.1.113883.5.1008 Geen Informatie

RouteOfAdministrationCodelist

Valueset OID: 2.16.840.1.113883.2.4.3.11.60.40.2.9.12.1 Binding:
Conceptname Codesystem name Codesystem OID
Alle waarden G-Standaard Toedieningswegen 2.16.840.1.113883.2.4.4.9

TimeOfDayCodelist

Valueset OID: 2.16.840.1.113883.2.4.3.11.60.40.2.9.12.3 Binding:
Conceptname Conceptcode Codesystem name Codesystem 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

WeekDayCodelist

Valueset OID: 2.16.840.1.113883.2.4.3.11.60.40.2.9.12.2 Binding:
Conceptname Conceptcode Codesystem name Codesystem 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

This information model in other releases

Information model references

This information model refers to

This information model is used in

Technical specifications in HL7v3 CDA and HL7 FHIR

To exchange information based on health and care information models, additional, more technical specifications are required.
Not every environment can handle the same technical specifications. For this reason, there are several types of technical specifications:

  • HL7® version 3 CDA compatible specifications, available through the Nictiz ART-DECOR® environment Artdecor.jpg
  • HL7® FHIR® compatible specifications, available through the Nictiz environment on the Simplifier FHIR Fhir.png

Downloads

This information model is also available as pdf file PDF.png or as spreadsheet Xlsx.png

About this information

The information in this wikipage is based on Release 2017
Conditions for use are located on the mainpage List2.png
This page is generated on 21/12/2018 14:05:53 with ZibExtraction v. 3.0.6929.24609


Back 16.png Back to HCIM list