TEMPLATE ED Clinical Knowledge Topic (ED Clinical Knowledge Topic)

TEMPLATE ID	ED Clinical Knowledge Topic
Concept	ED Clinical Knowledge Topic
Description	Not Specified
Purpose	Not Specified
References
Other Details (Language Independent)	MetaDataSet:Sample Set : Template metadata sample set
Language used	en
Citeable Identifier	1013.26.919
Root archetype id	openEHR-EHR-SECTION.clinical_knowledge_topic.v1
ED Clinical Knowledge Topic	ED Clinical Knowledge Topic: unknown
Order Set(s)	Order Set(s): *
Investigations and Analgesics ED order set	Investigations and Analgesics ED order set: unknown
Laboratory Investigations	Laboratory Investigations: *
Laboratory Order set module	Laboratory Order set module: unknown
Complete Blood Count with diff	Complete Blood Count with diff: Request for a health-related service to be supplied by a healthcare provider or agency. For example equipment request.
Request	Request: Description of the requested service.
Description
Service name	Service name: Identification of the service requested, by name. Coding of the 'Service name' with a coding system is desirable, if available. Complete Blood Count with diff
Reason for request	Reason for request: Describes the reason for the request. Coding of the 'Reason for request' with a coding system is desirable, if available.
Priority	Priority: Urgency of the request for service. Specific definitions of emergency and urgent will vary between clinical contexts, clinical systems and the nature of the request itself, so have not be defined in this archetype. If explicit timing is required then the Service period should be clearly stated. Routine STAT Urgent
Pending transition	Pending transition: To indicate if patient transition is dependent on the completion of this order.
Service direction	Service direction: Structured details of a single therapeutic direction for an ordered item, such as a laboratory test, diagnostic image etc.
Direction sequence	Direction sequence: The intended position of this direction within the overall sequence of directions. For example: ''1' '2', '3'. Where multiple dosage directions are expressed, the 'Direction sequence' makes the order in which they should be executed explicit. For example: (1) 1 tab daily for 3 days, (2) 1 tab twice daily for 4 days, (3) 1 tablet for 7 days. >=1
Timing ahs	Timing ahs: Structured information about the intended timing of a therapeutic or diagnostic activity
Frequency	Frequency: The frequency as how often, either by number of times per time period or interval between each scheduled activity, that the activity is to take place. or example: "q4h", "every 4 hours", "weekly", "every 2 days". Once Daily q12h q2days
Specific time	Specific time: A specific time or interval of time when the activity should occur. For example: "08:00" or "15:00-16:00". Time Interval of Time
Specific date	Specific date: The activity should take place on a specific date or a specific range of dates. For example: 'on 12 Jan 2017' or 'on 30 Oct 2017 to 6 Nov 2017'. Date Interval of Date
Specific day of week	Specific day of week: The activity should take place on a specific day of the week. For example: 'On Monday, Wednesday and Friday'. Monday Tuesday Wednesday Thursday Friday Saturday Sunday
Specific day of month	Specific day of month: The activity should take place on a specific day or interval of days of the month. For example: 'on the 3rd, 13th and 23rd of each month' or 'on the 1st to the 10th of each month'. Count1..31 Interval of CountLower constraint: 1..31 Upper constraint: 1..31
Specific event	Specific event: A specific, named time event that the activity should occur in relation to.
Event name	Event name: The name of the event that triggers the activity to take place. For example: "Before each meal", "at bedtime", "in the morning". It is understood that these event names may not equate to the same exact times in different cultures. Coding with a terminology, for example HL7 FHIR Named events, is recommended where appropriate.
Time offset	Time offset: The period of time before or after the named event when the activity should take place. Negative durations can be used to signify that the activity should be taken before a known event. For example:For example: '30 minutes after meal = meal + 30 minutes', '2 hours before bedtime = bedtime -2 hours'. '3 days after onset of menstruation = menstrual onset + 3 days', '2 weeks prior to admission= admission -2 weeks'.
On / off cycle	On / off cycle: A cycle of activity where an on-off pattern is required. For example: "Apply an ice pack on for 20 minutes, off for an hour, repeat" or For example: 'take for 1 week, omit 2 weeks, repeat 4 times'
On	On: The period of time for which the activity should take place.
Off	Off: The period of time for which the activity should NOT take place.
Repetitions	Repetitions: The number of repetitions of the on/off cycle.
Direction duration	Direction duration: The length of time for which this direction should be applied. For example: 'for 7 days','Indefinite'. An example of a set of multiple directions, with varying durations might be ... '1 tablet daily for 3 days, 2 tablets daily for 4 days, then 3 tablets Indefinite'. Coded Text Indefinite Indefinite - not to be discontinued Duration>=PT0S Text
Maximum number of services provided	Maximum number of services provided: The maximum number of services to be given for this direction. Example: 'Give once only' = 1 or '400mg 12hrly for 3 doses' = 3. >=1
Indefinite?	Indefinite?: The valid period for this request is open ended and has no date of expiry. Record as TRUE to record explicity that the request has no expiry date.
Information description	Information description: Description of the supplementary information.
Comment	Comment: Additional narrative about the service request not captured in other fields.
Protocol
Requestor Identifier	Requestor Identifier: The local ID assigned to the order by the healthcare provider or organisation requesting the service. This is also referred to as Placer Order Identifier.
Receiver identifier	Receiver identifier: The ID assigned to the order by the healthcare provider or organisation receiving the request for service. This is also referred to as Filler Order Identifier.
Request status	Request status: The status of the request for service as indicated by the requester. Status is used to denote whether this is the initial request, or a follow-up request to change or provide supplementary information.
Creatinine LEVEL	Creatinine LEVEL: Request for a health-related service to be supplied by a healthcare provider or agency. For example equipment request.
Request	Request: Description of the requested service.
Description
Service name	Service name: Identification of the service requested, by name. Coding of the 'Service name' with a coding system is desirable, if available. Creatinine LEVEL
Reason for request	Reason for request: Describes the reason for the request. Coding of the 'Reason for request' with a coding system is desirable, if available.
Priority	Priority: Urgency of the request for service. Specific definitions of emergency and urgent will vary between clinical contexts, clinical systems and the nature of the request itself, so have not be defined in this archetype. If explicit timing is required then the Service period should be clearly stated. Routine STAT Urgent
Pending transition	Pending transition: To indicate if patient transition is dependent on the completion of this order.
Service direction	Service direction: Structured details of a single therapeutic direction for an ordered item, such as a laboratory test, diagnostic image etc.
Direction sequence	Direction sequence: The intended position of this direction within the overall sequence of directions. For example: ''1' '2', '3'. Where multiple dosage directions are expressed, the 'Direction sequence' makes the order in which they should be executed explicit. For example: (1) 1 tab daily for 3 days, (2) 1 tab twice daily for 4 days, (3) 1 tablet for 7 days. >=1
Timing ahs	Timing ahs: Structured information about the intended timing of a therapeutic or diagnostic activity
Frequency	Frequency: The frequency as how often, either by number of times per time period or interval between each scheduled activity, that the activity is to take place. or example: "q4h", "every 4 hours", "weekly", "every 2 days". Once Daily q12h q2days
Specific time	Specific time: A specific time or interval of time when the activity should occur. For example: "08:00" or "15:00-16:00". Time Interval of Time
Specific date	Specific date: The activity should take place on a specific date or a specific range of dates. For example: 'on 12 Jan 2017' or 'on 30 Oct 2017 to 6 Nov 2017'. Date Interval of Date
Specific day of week	Specific day of week: The activity should take place on a specific day of the week. For example: 'On Monday, Wednesday and Friday'. Monday Tuesday Wednesday Thursday Friday Saturday Sunday
Specific day of month	Specific day of month: The activity should take place on a specific day or interval of days of the month. For example: 'on the 3rd, 13th and 23rd of each month' or 'on the 1st to the 10th of each month'. Count1..31 Interval of CountLower constraint: 1..31 Upper constraint: 1..31
Specific event	Specific event: A specific, named time event that the activity should occur in relation to.
Event name	Event name: The name of the event that triggers the activity to take place. For example: "Before each meal", "at bedtime", "in the morning". It is understood that these event names may not equate to the same exact times in different cultures. Coding with a terminology, for example HL7 FHIR Named events, is recommended where appropriate.
Time offset	Time offset: The period of time before or after the named event when the activity should take place. Negative durations can be used to signify that the activity should be taken before a known event. For example:For example: '30 minutes after meal = meal + 30 minutes', '2 hours before bedtime = bedtime -2 hours'. '3 days after onset of menstruation = menstrual onset + 3 days', '2 weeks prior to admission= admission -2 weeks'.
On / off cycle	On / off cycle: A cycle of activity where an on-off pattern is required. For example: "Apply an ice pack on for 20 minutes, off for an hour, repeat" or For example: 'take for 1 week, omit 2 weeks, repeat 4 times'
On	On: The period of time for which the activity should take place.
Off	Off: The period of time for which the activity should NOT take place.
Repetitions	Repetitions: The number of repetitions of the on/off cycle.
Direction duration	Direction duration: The length of time for which this direction should be applied. For example: 'for 7 days','Indefinite'. An example of a set of multiple directions, with varying durations might be ... '1 tablet daily for 3 days, 2 tablets daily for 4 days, then 3 tablets Indefinite'. Coded Text Indefinite Indefinite - not to be discontinued Duration>=PT0S Text
Maximum number of services provided	Maximum number of services provided: The maximum number of services to be given for this direction. Example: 'Give once only' = 1 or '400mg 12hrly for 3 doses' = 3. >=1
Indefinite?	Indefinite?: The valid period for this request is open ended and has no date of expiry. Record as TRUE to record explicity that the request has no expiry date.
Information description	Information description: Description of the supplementary information.
Comment	Comment: Additional narrative about the service request not captured in other fields.
Protocol
Requestor Identifier	Requestor Identifier: The local ID assigned to the order by the healthcare provider or organisation requesting the service. This is also referred to as Placer Order Identifier.
Receiver identifier	Receiver identifier: The ID assigned to the order by the healthcare provider or organisation receiving the request for service. This is also referred to as Filler Order Identifier.
Request status	Request status: The status of the request for service as indicated by the requester. Status is used to denote whether this is the initial request, or a follow-up request to change or provide supplementary information.
Diagnostic Imaging	Diagnostic Imaging: *
Diagnostic Imaging Order set module	Diagnostic Imaging Order set module: unknown
Chest Xray 2 projections	Chest Xray 2 projections: Request for a health-related service to be supplied by a healthcare provider or agency. For example equipment request.
Request	Request: Description of the requested service.
Description
Service name	Service name: Identification of the service requested, by name. Coding of the 'Service name' with a coding system is desirable, if available. Chest Xray 2 projections
Reason for request	Reason for request: Describes the reason for the request. Coding of the 'Reason for request' with a coding system is desirable, if available.
Priority	Priority: Urgency of the request for service. Specific definitions of emergency and urgent will vary between clinical contexts, clinical systems and the nature of the request itself, so have not be defined in this archetype. If explicit timing is required then the Service period should be clearly stated. Routine STAT Urgent
Pending transition	Pending transition: To indicate if patient transition is dependent on the completion of this order.
Service direction	Service direction: Structured details of a single therapeutic direction for an ordered item, such as a laboratory test, diagnostic image etc.
Direction sequence	Direction sequence: The intended position of this direction within the overall sequence of directions. For example: ''1' '2', '3'. Where multiple dosage directions are expressed, the 'Direction sequence' makes the order in which they should be executed explicit. For example: (1) 1 tab daily for 3 days, (2) 1 tab twice daily for 4 days, (3) 1 tablet for 7 days. >=1
Timing ahs	Timing ahs: Structured information about the intended timing of a therapeutic or diagnostic activity
Frequency	Frequency: The frequency as how often, either by number of times per time period or interval between each scheduled activity, that the activity is to take place. or example: "q4h", "every 4 hours", "weekly", "every 2 days". Once
Specific time	Specific time: A specific time or interval of time when the activity should occur. For example: "08:00" or "15:00-16:00". Time Interval of Time
Specific date	Specific date: The activity should take place on a specific date or a specific range of dates. For example: 'on 12 Jan 2017' or 'on 30 Oct 2017 to 6 Nov 2017'. Date Interval of Date
Specific day of week	Specific day of week: The activity should take place on a specific day of the week. For example: 'On Monday, Wednesday and Friday'. Monday Tuesday Wednesday Thursday Friday Saturday Sunday
Specific day of month	Specific day of month: The activity should take place on a specific day or interval of days of the month. For example: 'on the 3rd, 13th and 23rd of each month' or 'on the 1st to the 10th of each month'. Count1..31 Interval of CountLower constraint: 1..31 Upper constraint: 1..31
Specific event	Specific event: A specific, named time event that the activity should occur in relation to.
Event name	Event name: The name of the event that triggers the activity to take place. For example: "Before each meal", "at bedtime", "in the morning". It is understood that these event names may not equate to the same exact times in different cultures. Coding with a terminology, for example HL7 FHIR Named events, is recommended where appropriate.
Time offset	Time offset: The period of time before or after the named event when the activity should take place. Negative durations can be used to signify that the activity should be taken before a known event. For example:For example: '30 minutes after meal = meal + 30 minutes', '2 hours before bedtime = bedtime -2 hours'. '3 days after onset of menstruation = menstrual onset + 3 days', '2 weeks prior to admission= admission -2 weeks'.
On / off cycle	On / off cycle: A cycle of activity where an on-off pattern is required. For example: "Apply an ice pack on for 20 minutes, off for an hour, repeat" or For example: 'take for 1 week, omit 2 weeks, repeat 4 times'
On	On: The period of time for which the activity should take place.
Off	Off: The period of time for which the activity should NOT take place.
Repetitions	Repetitions: The number of repetitions of the on/off cycle.
Direction duration	Direction duration: The length of time for which this direction should be applied. For example: 'for 7 days','Indefinite'. An example of a set of multiple directions, with varying durations might be ... '1 tablet daily for 3 days, 2 tablets daily for 4 days, then 3 tablets Indefinite'. Coded Text Indefinite Indefinite - not to be discontinued Duration>=PT0S Text
Maximum number of services provided	Maximum number of services provided: The maximum number of services to be given for this direction. Example: 'Give once only' = 1 or '400mg 12hrly for 3 doses' = 3. >=1
Indefinite?	Indefinite?: The valid period for this request is open ended and has no date of expiry. Record as TRUE to record explicity that the request has no expiry date.
Information description	Information description: Description of the supplementary information.
Comment	Comment: Additional narrative about the service request not captured in other fields.
Protocol
Requestor Identifier	Requestor Identifier: The local ID assigned to the order by the healthcare provider or organisation requesting the service. This is also referred to as Placer Order Identifier.
Receiver identifier	Receiver identifier: The ID assigned to the order by the healthcare provider or organisation receiving the request for service. This is also referred to as Filler Order Identifier.
Request status	Request status: The status of the request for service as indicated by the requester. Status is used to denote whether this is the initial request, or a follow-up request to change or provide supplementary information.
Chest Xray 1 projection	Chest Xray 1 projection: Request for a health-related service to be supplied by a healthcare provider or agency. For example equipment request.
Request	Request: Description of the requested service.
Description
Service name	Service name: Identification of the service requested, by name. Coding of the 'Service name' with a coding system is desirable, if available. Chest Xray 1 projection
Reason for request	Reason for request: Describes the reason for the request. Coding of the 'Reason for request' with a coding system is desirable, if available.
Priority	Priority: Urgency of the request for service. Specific definitions of emergency and urgent will vary between clinical contexts, clinical systems and the nature of the request itself, so have not be defined in this archetype. If explicit timing is required then the Service period should be clearly stated. Routine STAT Urgent
Pending transition	Pending transition: To indicate if patient transition is dependent on the completion of this order.
Service direction	Service direction: Structured details of a single therapeutic direction for an ordered item, such as a laboratory test, diagnostic image etc.
Direction sequence	Direction sequence: The intended position of this direction within the overall sequence of directions. For example: ''1' '2', '3'. Where multiple dosage directions are expressed, the 'Direction sequence' makes the order in which they should be executed explicit. For example: (1) 1 tab daily for 3 days, (2) 1 tab twice daily for 4 days, (3) 1 tablet for 7 days. >=1
Timing ahs	Timing ahs: Structured information about the intended timing of a therapeutic or diagnostic activity
Frequency	Frequency: The frequency as how often, either by number of times per time period or interval between each scheduled activity, that the activity is to take place. or example: "q4h", "every 4 hours", "weekly", "every 2 days". Once
Specific time	Specific time: A specific time or interval of time when the activity should occur. For example: "08:00" or "15:00-16:00". Time Interval of Time
Specific date	Specific date: The activity should take place on a specific date or a specific range of dates. For example: 'on 12 Jan 2017' or 'on 30 Oct 2017 to 6 Nov 2017'. Date Interval of Date
Specific day of week	Specific day of week: The activity should take place on a specific day of the week. For example: 'On Monday, Wednesday and Friday'. Monday Tuesday Wednesday Thursday Friday Saturday Sunday
Specific day of month	Specific day of month: The activity should take place on a specific day or interval of days of the month. For example: 'on the 3rd, 13th and 23rd of each month' or 'on the 1st to the 10th of each month'. Count1..31 Interval of CountLower constraint: 1..31 Upper constraint: 1..31
Specific event	Specific event: A specific, named time event that the activity should occur in relation to.
Event name	Event name: The name of the event that triggers the activity to take place. For example: "Before each meal", "at bedtime", "in the morning". It is understood that these event names may not equate to the same exact times in different cultures. Coding with a terminology, for example HL7 FHIR Named events, is recommended where appropriate.
Time offset	Time offset: The period of time before or after the named event when the activity should take place. Negative durations can be used to signify that the activity should be taken before a known event. For example:For example: '30 minutes after meal = meal + 30 minutes', '2 hours before bedtime = bedtime -2 hours'. '3 days after onset of menstruation = menstrual onset + 3 days', '2 weeks prior to admission= admission -2 weeks'.
On / off cycle	On / off cycle: A cycle of activity where an on-off pattern is required. For example: "Apply an ice pack on for 20 minutes, off for an hour, repeat" or For example: 'take for 1 week, omit 2 weeks, repeat 4 times'
On	On: The period of time for which the activity should take place.
Off	Off: The period of time for which the activity should NOT take place.
Repetitions	Repetitions: The number of repetitions of the on/off cycle.
Direction duration	Direction duration: The length of time for which this direction should be applied. For example: 'for 7 days','Indefinite'. An example of a set of multiple directions, with varying durations might be ... '1 tablet daily for 3 days, 2 tablets daily for 4 days, then 3 tablets Indefinite'. Coded Text Indefinite Indefinite - not to be discontinued Duration>=PT0S Text
Maximum number of services provided	Maximum number of services provided: The maximum number of services to be given for this direction. Example: 'Give once only' = 1 or '400mg 12hrly for 3 doses' = 3. >=1
Indefinite?	Indefinite?: The valid period for this request is open ended and has no date of expiry. Record as TRUE to record explicity that the request has no expiry date.
Information description	Information description: Description of the supplementary information.
Comment	Comment: Additional narrative about the service request not captured in other fields.
Protocol
Requestor Identifier	Requestor Identifier: The local ID assigned to the order by the healthcare provider or organisation requesting the service. This is also referred to as Placer Order Identifier.
Receiver identifier	Receiver identifier: The ID assigned to the order by the healthcare provider or organisation receiving the request for service. This is also referred to as Filler Order Identifier.
Request status	Request status: The status of the request for service as indicated by the requester. Status is used to denote whether this is the initial request, or a follow-up request to change or provide supplementary information.
Medications	Medications: *
Pain Medication Order set module	Pain Medication Order set module: unknown
acetaminophen tablet	acetaminophen tablet: An order for a medication, vaccine, nutritional product or other therapeutic item for an identified individual.
Order	Order: Details of the requested order.
Description
Medication item	Medication item: Name of the medication, vaccine or other therapeutic/prescribable item being ordered. Depending on the prescribing context this field could be used for either generic- or product-based prescribing. This data field can be used to record tightly bound orders of different medications when they are prescribed as a single pack. It is strongly recommended that the 'Medication item' be coded with a terminology capable of triggering decision support, where possible. The extent of coding may vary from the simple name of the medication item through to structured details about the actual medication pack to be used. Free text entry should only be used if there is no appropriate terminology available. acetaminophen tablet
Therapeutic direction modified	Therapeutic direction modified: Structured details of a single therapeutic direction for an ordered item, such as a medication or blood transfusion order.
Direction sequence	Direction sequence: The intended position of this direction within the overall sequence of directions. For example: ''1' '2', '3'. Where multiple dosage directions are expressed, the 'Direction sequence' makes the order in which they should be executed explicit. For example: (1) 1 tab daily for 3 days, (2) 1 tab twice daily for 4 days, (3) 1 tablet for 7 days. >=1
Dosage	Dosage: *
Dosage sequence	Dosage sequence: The intended position of this dosage within the overall sequence of dosages.
Dose amount	Dose amount: The value of the amount of medication administered at one time, as a real number, or range of real numbers, and associated with the Dose unit. For example: 1, 1.5, 0.125 or 1-2, 12.5-20.5 325 500 650 975 1000
Dose unit	Dose unit: The unit which is associated with the Dose amount. For example: 'tablet','mg'. Coding of the dose unit with a terminology is preferred, where possible. mg
Timing ahs	Timing ahs: Structured information about the intended timing of a therapeutic or diagnostic activity
Frequency	Frequency: The frequency as how often, either by number of times per time period or interval between each scheduled activity, that the activity is to take place. or example: "q4h", "every 4 hours", "weekly", "every 2 days". bid daily once q4h q6h
Specific time	Specific time: A specific time or interval of time when the activity should occur. For example: "08:00" or "15:00-16:00". Time Interval of Time
Specific date	Specific date: The activity should take place on a specific date or a specific range of dates. For example: 'on 12 Jan 2017' or 'on 30 Oct 2017 to 6 Nov 2017'. Date Interval of Date
Specific day of week	Specific day of week: The activity should take place on a specific day of the week. For example: 'On Monday, Wednesday and Friday'. Monday Tuesday Wednesday Thursday Friday Saturday Sunday
Specific day of month	Specific day of month: The activity should take place on a specific day or interval of days of the month. For example: 'on the 3rd, 13th and 23rd of each month' or 'on the 1st to the 10th of each month'. Count1..31 Interval of CountLower constraint: 1..31 Upper constraint: 1..31
PRN	PRN: Record as True if the activity should only occur when the "'As required' criterion" is met. Termed 'PRN' ("pro re nata", latin: "as the situation arises") or 'PN' ("per necessare", latin: "when required") in some cultures.
PRN indication	PRN indication: The condition which triggers an 'As required' activity. For example: "for pain". for pain for fever [...]
Specific event	Specific event: A specific, named time event that the activity should occur in relation to.
Event name	Event name: The name of the event that triggers the activity to take place. For example: "Before each meal", "at bedtime", "in the morning". It is understood that these event names may not equate to the same exact times in different cultures. Coding with a terminology, for example HL7 FHIR Named events, is recommended where appropriate.
Time offset	Time offset: The period of time before or after the named event when the activity should take place. Negative durations can be used to signify that the activity should be taken before a known event. For example:For example: '30 minutes after meal = meal + 30 minutes', '2 hours before bedtime = bedtime -2 hours'. '3 days after onset of menstruation = menstrual onset + 3 days', '2 weeks prior to admission= admission -2 weeks'.
On / off cycle	On / off cycle: A cycle of activity where an on-off pattern is required. For example: "Apply an ice pack on for 20 minutes, off for an hour, repeat" or For example: 'take for 1 week, omit 2 weeks, repeat 4 times'
On	On: The period of time for which the activity should take place.
Off	Off: The period of time for which the activity should NOT take place.
Repetitions	Repetitions: The number of repetitions of the on/off cycle.
Route	Route: The route by which the ordered item is to be administered into the subject's body. or example: 'oral', 'intravenous', or 'topical'. Coding of the route with a terminology is preferred, where possible. Multiple potential routes may be specified. PO
Direction duration	Direction duration: The length of time for which this direction should be applied. For example: 'for 7 days','Indefinite'. An example of a set of multiple directions, with varying durations might be ... '1 tablet daily for 3 days, 2 tablets daily for 4 days, then 3 tablets Indefinite'. Coded Text Indefinite Indefinite - not to be discontinued Duration>=PT0S Text
Maximum number of administrations	Maximum number of administrations: The maximum number of administrations to be given for this direction. Example: 'Give once only' = 1 or '400mg 12hrly for 3 doses' = 3. >=1
Order details	Order details: Details about the whole medication order.
Priority	Priority: An indicator of the urgency with which the ordered item should be dispensed. For example 'Urgent'. This is left to be templated or specialised according to local valuesets. Some jurisdictions allow instructions to dispense to be marked as 'urgent' so that the dispensary handles them quickly.
Order start date/time	Order start date/time: The date and optional time to commence use of the ordered item.
Order stop date/time	Order stop date/time: The date and optional time when it is planned to cease use of the ordered item.
Order start criterion	Order start criterion: A condition which, when met, requires the commencement of administration or use. For example: 'Start if symptoms recur'. This is intended for a general pre-condition which should trigger the whole medication course to be started, and not for 'as required' administrations of an ongoing order.
Order stop criterion	Order stop criterion: A condition which, when met, requires the cessation of administration or use. For example: 'Stop after symptoms disappear''.
Additional instruction	Additional instruction: An additional instruction on how to use or store the ordered item. For example: precautions as 'take with food', 'Avoid grapefruit', 'Dissolve in water', 'store in a cool, dry place'. This data element allows multiple occurrences and should be coded with a reference terminology, where possible.
Medication safety	Medication safety: Details about medication safety for the ordered item.
Maximum dose	Maximum dose: Details about the maximum, cumulative dose allowed over a defined period for the ordered item. For example: 'up to 1gram per day'. This cluster allows multiple occurrences to enable representation of multiple maximum doses that apply to different time periods. Lifetime maximum dose should not be carried here as it refers to multiple orders over time.
Maximum amount	Maximum amount: The maximum, cumulative amount of medication which should be administered within the allowed period. The unit for this amount is carried in Maximum amount unit. For example: 1, 1.5, 0.125. >=0 (UCUM: 1)
Maximum amount unit	Maximum amount unit: The unit for the maximum amount allowed. For example: 'tablet','mg'. Coding of the dose unit with a terminology is preferred, where possible. mg/day
Protocol	Protocol: The amount and units of the medication, vaccine or other therapeutic good to be used or administered at one time.
Order identifier	Order identifier: Unique identifier for the medication order. This data element allows for multiple occurrences to be defined more explicitly at run-time, if required.
acetylsalicylic acid tablet	acetylsalicylic acid tablet: An order for a medication, vaccine, nutritional product or other therapeutic item for an identified individual.
Order	Order: Details of the requested order.
Description
Medication item	Medication item: Name of the medication, vaccine or other therapeutic/prescribable item being ordered. Depending on the prescribing context this field could be used for either generic- or product-based prescribing. This data field can be used to record tightly bound orders of different medications when they are prescribed as a single pack. It is strongly recommended that the 'Medication item' be coded with a terminology capable of triggering decision support, where possible. The extent of coding may vary from the simple name of the medication item through to structured details about the actual medication pack to be used. Free text entry should only be used if there is no appropriate terminology available. acetylsalicylic acid tablet
Therapeutic direction modified	Therapeutic direction modified: Structured details of a single therapeutic direction for an ordered item, such as a medication or blood transfusion order.
Direction sequence	Direction sequence: The intended position of this direction within the overall sequence of directions. For example: ''1' '2', '3'. Where multiple dosage directions are expressed, the 'Direction sequence' makes the order in which they should be executed explicit. For example: (1) 1 tab daily for 3 days, (2) 1 tab twice daily for 4 days, (3) 1 tablet for 7 days. >=1
Dosage	Dosage: *
Dosage sequence	Dosage sequence: The intended position of this dosage within the overall sequence of dosages.
Dose amount	Dose amount: The value of the amount of medication administered at one time, as a real number, or range of real numbers, and associated with the Dose unit. For example: 1, 1.5, 0.125 or 1-2, 12.5-20.5 81 325 650
Dose unit	Dose unit: The unit which is associated with the Dose amount. For example: 'tablet','mg'. Coding of the dose unit with a terminology is preferred, where possible. mg
Timing ahs	Timing ahs: Structured information about the intended timing of a therapeutic or diagnostic activity
Frequency	Frequency: The frequency as how often, either by number of times per time period or interval between each scheduled activity, that the activity is to take place. or example: "q4h", "every 4 hours", "weekly", "every 2 days". daily
Specific time	Specific time: A specific time or interval of time when the activity should occur. For example: "08:00" or "15:00-16:00". Time Interval of Time
Specific date	Specific date: The activity should take place on a specific date or a specific range of dates. For example: 'on 12 Jan 2017' or 'on 30 Oct 2017 to 6 Nov 2017'. Date Interval of Date
Specific day of week	Specific day of week: The activity should take place on a specific day of the week. For example: 'On Monday, Wednesday and Friday'. Monday Tuesday Wednesday Thursday Friday Saturday Sunday
Specific day of month	Specific day of month: The activity should take place on a specific day or interval of days of the month. For example: 'on the 3rd, 13th and 23rd of each month' or 'on the 1st to the 10th of each month'. Count1..31 Interval of CountLower constraint: 1..31 Upper constraint: 1..31
PRN	PRN: Record as True if the activity should only occur when the "'As required' criterion" is met. Termed 'PRN' ("pro re nata", latin: "as the situation arises") or 'PN' ("per necessare", latin: "when required") in some cultures.
PRN indication	PRN indication: The condition which triggers an 'As required' activity. For example: "for pain".
Specific event	Specific event: A specific, named time event that the activity should occur in relation to.
Event name	Event name: The name of the event that triggers the activity to take place. For example: "Before each meal", "at bedtime", "in the morning". It is understood that these event names may not equate to the same exact times in different cultures. Coding with a terminology, for example HL7 FHIR Named events, is recommended where appropriate.
Time offset	Time offset: The period of time before or after the named event when the activity should take place. Negative durations can be used to signify that the activity should be taken before a known event. For example:For example: '30 minutes after meal = meal + 30 minutes', '2 hours before bedtime = bedtime -2 hours'. '3 days after onset of menstruation = menstrual onset + 3 days', '2 weeks prior to admission= admission -2 weeks'.
On / off cycle	On / off cycle: A cycle of activity where an on-off pattern is required. For example: "Apply an ice pack on for 20 minutes, off for an hour, repeat" or For example: 'take for 1 week, omit 2 weeks, repeat 4 times'
On	On: The period of time for which the activity should take place.
Off	Off: The period of time for which the activity should NOT take place.
Repetitions	Repetitions: The number of repetitions of the on/off cycle.
Route	Route: The route by which the ordered item is to be administered into the subject's body. or example: 'oral', 'intravenous', or 'topical'. Coding of the route with a terminology is preferred, where possible. Multiple potential routes may be specified. PO
Direction duration	Direction duration: The length of time for which this direction should be applied. For example: 'for 7 days','Indefinite'. An example of a set of multiple directions, with varying durations might be ... '1 tablet daily for 3 days, 2 tablets daily for 4 days, then 3 tablets Indefinite'. Coded Text Indefinite Indefinite - not to be discontinued Duration>=PT0S Text
Maximum number of administrations	Maximum number of administrations: The maximum number of administrations to be given for this direction. Example: 'Give once only' = 1 or '400mg 12hrly for 3 doses' = 3. >=1
Order details	Order details: Details about the whole medication order.
Priority	Priority: An indicator of the urgency with which the ordered item should be dispensed. For example 'Urgent'. This is left to be templated or specialised according to local valuesets. Some jurisdictions allow instructions to dispense to be marked as 'urgent' so that the dispensary handles them quickly.
Order start date/time	Order start date/time: The date and optional time to commence use of the ordered item.
Order stop date/time	Order stop date/time: The date and optional time when it is planned to cease use of the ordered item.
Order start criterion	Order start criterion: A condition which, when met, requires the commencement of administration or use. For example: 'Start if symptoms recur'. This is intended for a general pre-condition which should trigger the whole medication course to be started, and not for 'as required' administrations of an ongoing order.
Order stop criterion	Order stop criterion: A condition which, when met, requires the cessation of administration or use. For example: 'Stop after symptoms disappear''.
Additional instruction	Additional instruction: An additional instruction on how to use or store the ordered item. For example: precautions as 'take with food', 'Avoid grapefruit', 'Dissolve in water', 'store in a cool, dry place'. This data element allows multiple occurrences and should be coded with a reference terminology, where possible.
Protocol	Protocol: The amount and units of the medication, vaccine or other therapeutic good to be used or administered at one time.
Order identifier	Order identifier: Unique identifier for the medication order. This data element allows for multiple occurrences to be defined more explicitly at run-time, if required.
fentanyl injection	fentanyl injection: An order for a medication, vaccine, nutritional product or other therapeutic item for an identified individual.
Order	Order: Details of the requested order.
Description
Medication item	Medication item: Name of the medication, vaccine or other therapeutic/prescribable item being ordered. Depending on the prescribing context this field could be used for either generic- or product-based prescribing. This data field can be used to record tightly bound orders of different medications when they are prescribed as a single pack. It is strongly recommended that the 'Medication item' be coded with a terminology capable of triggering decision support, where possible. The extent of coding may vary from the simple name of the medication item through to structured details about the actual medication pack to be used. Free text entry should only be used if there is no appropriate terminology available. fentanyl injection
Therapeutic direction modified	Therapeutic direction modified: Structured details of a single therapeutic direction for an ordered item, such as a medication or blood transfusion order.
Direction sequence	Direction sequence: The intended position of this direction within the overall sequence of directions. For example: ''1' '2', '3'. Where multiple dosage directions are expressed, the 'Direction sequence' makes the order in which they should be executed explicit. For example: (1) 1 tab daily for 3 days, (2) 1 tab twice daily for 4 days, (3) 1 tablet for 7 days. >=1
Dosage	Dosage: *
Dosage sequence	Dosage sequence: The intended position of this dosage within the overall sequence of dosages.
Dose amount	Dose amount: The value of the amount of medication administered at one time, as a real number, or range of real numbers, and associated with the Dose unit. For example: 1, 1.5, 0.125 or 1-2, 12.5-20.5 25 50
Dose unit	Dose unit: The unit which is associated with the Dose amount. For example: 'tablet','mg'. Coding of the dose unit with a terminology is preferred, where possible. micrograms
Timing ahs	Timing ahs: Structured information about the intended timing of a therapeutic or diagnostic activity
Frequency	Frequency: The frequency as how often, either by number of times per time period or interval between each scheduled activity, that the activity is to take place. or example: "q4h", "every 4 hours", "weekly", "every 2 days". once q1h q2h
Specific time	Specific time: A specific time or interval of time when the activity should occur. For example: "08:00" or "15:00-16:00". Time Interval of Time
Specific date	Specific date: The activity should take place on a specific date or a specific range of dates. For example: 'on 12 Jan 2017' or 'on 30 Oct 2017 to 6 Nov 2017'. Date Interval of Date
Specific day of week	Specific day of week: The activity should take place on a specific day of the week. For example: 'On Monday, Wednesday and Friday'. Monday Tuesday Wednesday Thursday Friday Saturday Sunday
Specific day of month	Specific day of month: The activity should take place on a specific day or interval of days of the month. For example: 'on the 3rd, 13th and 23rd of each month' or 'on the 1st to the 10th of each month'. Count1..31 Interval of CountLower constraint: 1..31 Upper constraint: 1..31
PRN	PRN: Record as True if the activity should only occur when the "'As required' criterion" is met. Termed 'PRN' ("pro re nata", latin: "as the situation arises") or 'PN' ("per necessare", latin: "when required") in some cultures.
PRN indication	PRN indication: The condition which triggers an 'As required' activity. For example: "for pain". for pain [...]
Specific event	Specific event: A specific, named time event that the activity should occur in relation to.
Event name	Event name: The name of the event that triggers the activity to take place. For example: "Before each meal", "at bedtime", "in the morning". It is understood that these event names may not equate to the same exact times in different cultures. Coding with a terminology, for example HL7 FHIR Named events, is recommended where appropriate.
Time offset	Time offset: The period of time before or after the named event when the activity should take place. Negative durations can be used to signify that the activity should be taken before a known event. For example:For example: '30 minutes after meal = meal + 30 minutes', '2 hours before bedtime = bedtime -2 hours'. '3 days after onset of menstruation = menstrual onset + 3 days', '2 weeks prior to admission= admission -2 weeks'.
On / off cycle	On / off cycle: A cycle of activity where an on-off pattern is required. For example: "Apply an ice pack on for 20 minutes, off for an hour, repeat" or For example: 'take for 1 week, omit 2 weeks, repeat 4 times'
On	On: The period of time for which the activity should take place.
Off	Off: The period of time for which the activity should NOT take place.
Repetitions	Repetitions: The number of repetitions of the on/off cycle.
Route	Route: The route by which the ordered item is to be administered into the subject's body. or example: 'oral', 'intravenous', or 'topical'. Coding of the route with a terminology is preferred, where possible. Multiple potential routes may be specified. PO
Direction duration	Direction duration: The length of time for which this direction should be applied. For example: 'for 7 days','Indefinite'. An example of a set of multiple directions, with varying durations might be ... '1 tablet daily for 3 days, 2 tablets daily for 4 days, then 3 tablets Indefinite'. Coded Text Indefinite Indefinite - not to be discontinued Duration>=PT0S Text
Maximum number of administrations	Maximum number of administrations: The maximum number of administrations to be given for this direction. Example: 'Give once only' = 1 or '400mg 12hrly for 3 doses' = 3. >=1
Order details	Order details: Details about the whole medication order.
Priority	Priority: An indicator of the urgency with which the ordered item should be dispensed. For example 'Urgent'. This is left to be templated or specialised according to local valuesets. Some jurisdictions allow instructions to dispense to be marked as 'urgent' so that the dispensary handles them quickly.
Order start date/time	Order start date/time: The date and optional time to commence use of the ordered item.
Order stop date/time	Order stop date/time: The date and optional time when it is planned to cease use of the ordered item.
Order start criterion	Order start criterion: A condition which, when met, requires the commencement of administration or use. For example: 'Start if symptoms recur'. This is intended for a general pre-condition which should trigger the whole medication course to be started, and not for 'as required' administrations of an ongoing order.
Order stop criterion	Order stop criterion: A condition which, when met, requires the cessation of administration or use. For example: 'Stop after symptoms disappear''.
Additional instruction	Additional instruction: An additional instruction on how to use or store the ordered item. For example: precautions as 'take with food', 'Avoid grapefruit', 'Dissolve in water', 'store in a cool, dry place'. This data element allows multiple occurrences and should be coded with a reference terminology, where possible.
Protocol	Protocol: The amount and units of the medication, vaccine or other therapeutic good to be used or administered at one time.
Order identifier	Order identifier: Unique identifier for the medication order. This data element allows for multiple occurrences to be defined more explicitly at run-time, if required.
fentanyl Order set module	fentanyl Order set module: unknown
fentanyl injection	fentanyl injection: An order for a medication, vaccine, nutritional product or other therapeutic item for an identified individual.
Order	Order: Details of the requested order.
Description
Medication item	Medication item: Name of the medication, vaccine or other therapeutic/prescribable item being ordered. Depending on the prescribing context this field could be used for either generic- or product-based prescribing. This data field can be used to record tightly bound orders of different medications when they are prescribed as a single pack. It is strongly recommended that the 'Medication item' be coded with a terminology capable of triggering decision support, where possible. The extent of coding may vary from the simple name of the medication item through to structured details about the actual medication pack to be used. Free text entry should only be used if there is no appropriate terminology available. fentanyl injection
Therapeutic direction modified	Therapeutic direction modified: Structured details of a single therapeutic direction for an ordered item, such as a medication or blood transfusion order.
Direction sequence	Direction sequence: The intended position of this direction within the overall sequence of directions. For example: ''1' '2', '3'. Where multiple dosage directions are expressed, the 'Direction sequence' makes the order in which they should be executed explicit. For example: (1) 1 tab daily for 3 days, (2) 1 tab twice daily for 4 days, (3) 1 tablet for 7 days. >=1
Dosage	Dosage: *
Dosage sequence	Dosage sequence: The intended position of this dosage within the overall sequence of dosages.
Dose amount	Dose amount: The value of the amount of medication administered at one time, as a real number, or range of real numbers, and associated with the Dose unit. For example: 1, 1.5, 0.125 or 1-2, 12.5-20.5 25 50
Dose unit	Dose unit: The unit which is associated with the Dose amount. For example: 'tablet','mg'. Coding of the dose unit with a terminology is preferred, where possible. micrograms
Timing ahs	Timing ahs: Structured information about the intended timing of a therapeutic or diagnostic activity
Frequency	Frequency: The frequency as how often, either by number of times per time period or interval between each scheduled activity, that the activity is to take place. or example: "q4h", "every 4 hours", "weekly", "every 2 days". once q1h q2h
Specific time	Specific time: A specific time or interval of time when the activity should occur. For example: "08:00" or "15:00-16:00". Time Interval of Time
Specific date	Specific date: The activity should take place on a specific date or a specific range of dates. For example: 'on 12 Jan 2017' or 'on 30 Oct 2017 to 6 Nov 2017'. Date Interval of Date
Specific day of week	Specific day of week: The activity should take place on a specific day of the week. For example: 'On Monday, Wednesday and Friday'. Monday Tuesday Wednesday Thursday Friday Saturday Sunday
Specific day of month	Specific day of month: The activity should take place on a specific day or interval of days of the month. For example: 'on the 3rd, 13th and 23rd of each month' or 'on the 1st to the 10th of each month'. Count1..31 Interval of CountLower constraint: 1..31 Upper constraint: 1..31
PRN	PRN: Record as True if the activity should only occur when the "'As required' criterion" is met. Termed 'PRN' ("pro re nata", latin: "as the situation arises") or 'PN' ("per necessare", latin: "when required") in some cultures.
PRN indication	PRN indication: The condition which triggers an 'As required' activity. For example: "for pain". for pain [...]
Specific event	Specific event: A specific, named time event that the activity should occur in relation to.
Event name	Event name: The name of the event that triggers the activity to take place. For example: "Before each meal", "at bedtime", "in the morning". It is understood that these event names may not equate to the same exact times in different cultures. Coding with a terminology, for example HL7 FHIR Named events, is recommended where appropriate.
Time offset	Time offset: The period of time before or after the named event when the activity should take place. Negative durations can be used to signify that the activity should be taken before a known event. For example:For example: '30 minutes after meal = meal + 30 minutes', '2 hours before bedtime = bedtime -2 hours'. '3 days after onset of menstruation = menstrual onset + 3 days', '2 weeks prior to admission= admission -2 weeks'.
On / off cycle	On / off cycle: A cycle of activity where an on-off pattern is required. For example: "Apply an ice pack on for 20 minutes, off for an hour, repeat" or For example: 'take for 1 week, omit 2 weeks, repeat 4 times'
On	On: The period of time for which the activity should take place.
Off	Off: The period of time for which the activity should NOT take place.
Repetitions	Repetitions: The number of repetitions of the on/off cycle.
Route	Route: The route by which the ordered item is to be administered into the subject's body. or example: 'oral', 'intravenous', or 'topical'. Coding of the route with a terminology is preferred, where possible. Multiple potential routes may be specified. PO
Direction duration	Direction duration: The length of time for which this direction should be applied. For example: 'for 7 days','Indefinite'. An example of a set of multiple directions, with varying durations might be ... '1 tablet daily for 3 days, 2 tablets daily for 4 days, then 3 tablets Indefinite'. Coded Text Indefinite Indefinite - not to be discontinued Duration>=PT0S Text
Maximum number of administrations	Maximum number of administrations: The maximum number of administrations to be given for this direction. Example: 'Give once only' = 1 or '400mg 12hrly for 3 doses' = 3. >=1
Order details	Order details: Details about the whole medication order.
Priority	Priority: An indicator of the urgency with which the ordered item should be dispensed. For example 'Urgent'. This is left to be templated or specialised according to local valuesets. Some jurisdictions allow instructions to dispense to be marked as 'urgent' so that the dispensary handles them quickly.
Order start date/time	Order start date/time: The date and optional time to commence use of the ordered item.
Order stop date/time	Order stop date/time: The date and optional time when it is planned to cease use of the ordered item.
Order start criterion	Order start criterion: A condition which, when met, requires the commencement of administration or use. For example: 'Start if symptoms recur'. This is intended for a general pre-condition which should trigger the whole medication course to be started, and not for 'as required' administrations of an ongoing order.
Order stop criterion	Order stop criterion: A condition which, when met, requires the cessation of administration or use. For example: 'Stop after symptoms disappear''.
Additional instruction	Additional instruction: An additional instruction on how to use or store the ordered item. For example: precautions as 'take with food', 'Avoid grapefruit', 'Dissolve in water', 'store in a cool, dry place'. This data element allows multiple occurrences and should be coded with a reference terminology, where possible.
Protocol	Protocol: The amount and units of the medication, vaccine or other therapeutic good to be used or administered at one time.
Order identifier	Order identifier: Unique identifier for the medication order. This data element allows for multiple occurrences to be defined more explicitly at run-time, if required.
Chest Xray Module	Chest Xray Module: unknown
Chest Xray 1 projection	Chest Xray 1 projection: Request for a health-related service to be supplied by a healthcare provider or agency. For example equipment request.
Request	Request: Description of the requested service.
Description
Service name	Service name: Identification of the service requested, by name. Coding of the 'Service name' with a coding system is desirable, if available. Chest Xray 1 projection
Reason for request	Reason for request: Describes the reason for the request. Coding of the 'Reason for request' with a coding system is desirable, if available.
Priority	Priority: Urgency of the request for service. Specific definitions of emergency and urgent will vary between clinical contexts, clinical systems and the nature of the request itself, so have not be defined in this archetype. If explicit timing is required then the Service period should be clearly stated. Routine STAT Urgent
Pending transition	Pending transition: To indicate if patient transition is dependent on the completion of this order.
Service direction	Service direction: Structured details of a single therapeutic direction for an ordered item, such as a laboratory test, diagnostic image etc.
Direction sequence	Direction sequence: The intended position of this direction within the overall sequence of directions. For example: ''1' '2', '3'. Where multiple dosage directions are expressed, the 'Direction sequence' makes the order in which they should be executed explicit. For example: (1) 1 tab daily for 3 days, (2) 1 tab twice daily for 4 days, (3) 1 tablet for 7 days. >=1
Timing ahs	Timing ahs: Structured information about the intended timing of a therapeutic or diagnostic activity
Frequency	Frequency: The frequency as how often, either by number of times per time period or interval between each scheduled activity, that the activity is to take place. or example: "q4h", "every 4 hours", "weekly", "every 2 days".
Specific time	Specific time: A specific time or interval of time when the activity should occur. For example: "08:00" or "15:00-16:00". Time Interval of Time
Specific date	Specific date: The activity should take place on a specific date or a specific range of dates. For example: 'on 12 Jan 2017' or 'on 30 Oct 2017 to 6 Nov 2017'. Date Interval of Date
Specific day of week	Specific day of week: The activity should take place on a specific day of the week. For example: 'On Monday, Wednesday and Friday'. Monday Tuesday Wednesday Thursday Friday Saturday Sunday
Specific day of month	Specific day of month: The activity should take place on a specific day or interval of days of the month. For example: 'on the 3rd, 13th and 23rd of each month' or 'on the 1st to the 10th of each month'. Count1..31 Interval of CountLower constraint: 1..31 Upper constraint: 1..31
Specific event	Specific event: A specific, named time event that the activity should occur in relation to.
Event name	Event name: The name of the event that triggers the activity to take place. For example: "Before each meal", "at bedtime", "in the morning". It is understood that these event names may not equate to the same exact times in different cultures. Coding with a terminology, for example HL7 FHIR Named events, is recommended where appropriate.
Time offset	Time offset: The period of time before or after the named event when the activity should take place. Negative durations can be used to signify that the activity should be taken before a known event. For example:For example: '30 minutes after meal = meal + 30 minutes', '2 hours before bedtime = bedtime -2 hours'. '3 days after onset of menstruation = menstrual onset + 3 days', '2 weeks prior to admission= admission -2 weeks'.
On / off cycle	On / off cycle: A cycle of activity where an on-off pattern is required. For example: "Apply an ice pack on for 20 minutes, off for an hour, repeat" or For example: 'take for 1 week, omit 2 weeks, repeat 4 times'
On	On: The period of time for which the activity should take place.
Off	Off: The period of time for which the activity should NOT take place.
Repetitions	Repetitions: The number of repetitions of the on/off cycle.
Direction duration	Direction duration: The length of time for which this direction should be applied. For example: 'for 7 days','Indefinite'. An example of a set of multiple directions, with varying durations might be ... '1 tablet daily for 3 days, 2 tablets daily for 4 days, then 3 tablets Indefinite'. Coded Text Indefinite Indefinite - not to be discontinued Duration>=PT0S Text
Maximum number of services provided	Maximum number of services provided: The maximum number of services to be given for this direction. Example: 'Give once only' = 1 or '400mg 12hrly for 3 doses' = 3. >=1
Indefinite?	Indefinite?: The valid period for this request is open ended and has no date of expiry. Record as TRUE to record explicity that the request has no expiry date.
Information description	Information description: Description of the supplementary information.
Comment	Comment: Additional narrative about the service request not captured in other fields.
Protocol
Requestor Identifier	Requestor Identifier: The local ID assigned to the order by the healthcare provider or organisation requesting the service. This is also referred to as Placer Order Identifier.
Receiver identifier	Receiver identifier: The ID assigned to the order by the healthcare provider or organisation receiving the request for service. This is also referred to as Filler Order Identifier.
Request status	Request status: The status of the request for service as indicated by the requester. Status is used to denote whether this is the initial request, or a follow-up request to change or provide supplementary information.
Chest Xray 2 projections	Chest Xray 2 projections: Request for a health-related service to be supplied by a healthcare provider or agency. For example equipment request.
Request	Request: Description of the requested service.
Description
Service name	Service name: Identification of the service requested, by name. Coding of the 'Service name' with a coding system is desirable, if available. Chest Xray 2 projections
Reason for request	Reason for request: Describes the reason for the request. Coding of the 'Reason for request' with a coding system is desirable, if available.
Priority	Priority: Urgency of the request for service. Specific definitions of emergency and urgent will vary between clinical contexts, clinical systems and the nature of the request itself, so have not be defined in this archetype. If explicit timing is required then the Service period should be clearly stated. Routine STAT Urgent
Pending transition	Pending transition: To indicate if patient transition is dependent on the completion of this order.
Service direction	Service direction: Structured details of a single therapeutic direction for an ordered item, such as a laboratory test, diagnostic image etc.
Direction sequence	Direction sequence: The intended position of this direction within the overall sequence of directions. For example: ''1' '2', '3'. Where multiple dosage directions are expressed, the 'Direction sequence' makes the order in which they should be executed explicit. For example: (1) 1 tab daily for 3 days, (2) 1 tab twice daily for 4 days, (3) 1 tablet for 7 days. >=1
Timing ahs	Timing ahs: Structured information about the intended timing of a therapeutic or diagnostic activity
Frequency	Frequency: The frequency as how often, either by number of times per time period or interval between each scheduled activity, that the activity is to take place. or example: "q4h", "every 4 hours", "weekly", "every 2 days".
Specific time	Specific time: A specific time or interval of time when the activity should occur. For example: "08:00" or "15:00-16:00". Time Interval of Time
Specific date	Specific date: The activity should take place on a specific date or a specific range of dates. For example: 'on 12 Jan 2017' or 'on 30 Oct 2017 to 6 Nov 2017'. Date Interval of Date
Specific day of week	Specific day of week: The activity should take place on a specific day of the week. For example: 'On Monday, Wednesday and Friday'. Monday Tuesday Wednesday Thursday Friday Saturday Sunday
Specific day of month	Specific day of month: The activity should take place on a specific day or interval of days of the month. For example: 'on the 3rd, 13th and 23rd of each month' or 'on the 1st to the 10th of each month'. Count1..31 Interval of CountLower constraint: 1..31 Upper constraint: 1..31
Specific event	Specific event: A specific, named time event that the activity should occur in relation to.
Event name	Event name: The name of the event that triggers the activity to take place. For example: "Before each meal", "at bedtime", "in the morning". It is understood that these event names may not equate to the same exact times in different cultures. Coding with a terminology, for example HL7 FHIR Named events, is recommended where appropriate.
Time offset	Time offset: The period of time before or after the named event when the activity should take place. Negative durations can be used to signify that the activity should be taken before a known event. For example:For example: '30 minutes after meal = meal + 30 minutes', '2 hours before bedtime = bedtime -2 hours'. '3 days after onset of menstruation = menstrual onset + 3 days', '2 weeks prior to admission= admission -2 weeks'.
On / off cycle	On / off cycle: A cycle of activity where an on-off pattern is required. For example: "Apply an ice pack on for 20 minutes, off for an hour, repeat" or For example: 'take for 1 week, omit 2 weeks, repeat 4 times'
On	On: The period of time for which the activity should take place.
Off	Off: The period of time for which the activity should NOT take place.
Repetitions	Repetitions: The number of repetitions of the on/off cycle.
Direction duration	Direction duration: The length of time for which this direction should be applied. For example: 'for 7 days','Indefinite'. An example of a set of multiple directions, with varying durations might be ... '1 tablet daily for 3 days, 2 tablets daily for 4 days, then 3 tablets Indefinite'. Coded Text Indefinite Indefinite - not to be discontinued Duration>=PT0S Text
Maximum number of services provided	Maximum number of services provided: The maximum number of services to be given for this direction. Example: 'Give once only' = 1 or '400mg 12hrly for 3 doses' = 3. >=1
Indefinite?	Indefinite?: The valid period for this request is open ended and has no date of expiry. Record as TRUE to record explicity that the request has no expiry date.
Information description	Information description: Description of the supplementary information.
Comment	Comment: Additional narrative about the service request not captured in other fields.
Protocol
Requestor Identifier	Requestor Identifier: The local ID assigned to the order by the healthcare provider or organisation requesting the service. This is also referred to as Placer Order Identifier.
Receiver identifier	Receiver identifier: The ID assigned to the order by the healthcare provider or organisation receiving the request for service. This is also referred to as Filler Order Identifier.
Request status	Request status: The status of the request for service as indicated by the requester. Status is used to denote whether this is the initial request, or a follow-up request to change or provide supplementary information.