| TEMPLATE ID | Creatinine LEVEL |
|---|---|
| Concept | Creatinine LEVEL |
| Description | Not Specified |
| Purpose | Not Specified |
| References | |
| Other Details (Language Independent) |
|
| Language used | en |
| Citeable Identifier | 1013.26.910 |
| Root archetype id | openEHR-EHR-INSTRUCTION.diagnostic_imaging_request.v2 |
| 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.
|
| 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.
|
| 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".
|
| 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'.
|
| 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'.
|
| 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'.
|
| 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'.
|
| 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. |