Keywords
Table of contents
  1. 1. Clinical Trial
  2. 2. Routine Documentation
  3. 3. Registry/Cohort Study
  4. 4. Quality Assurance
  5. 5. Data Standard
    1. 5.1. Common Data Elements
      1. Released Standard
      1. Draft Standard
      1. Deprecated Standard
    1. 5.2. Scores & Instruments
      1. Released Standard
      1. Draft Standard
      1. Deprecated Standard
    1. 5.3. Classification
      1. Released Standard
      1. Draft Standard
      1. Deprecated Standard
    1. 5.4. Archetypes
      1. Published
  6. 6. Patient-Reported Outcome
  7. 7. Medical Specialty
Selected data models

You must log in to select data models for download or further analysis.

- 7/9/17 - 1 form, 1 itemgroup, 7 items, 4 languages
Itemgroup: openEHR-EHR-OBSERVATION.glasgow_coma_scale.v1.xml
Derived from www.openehr.org . Use to record clinical responses of an adult subject of care to stimuli. It is commonly used to establish a baseline conscious state and neurological function assessment and/or to detect patients who may require immediate medical intervention. The Glasgow coma scale has three subscales E (eye), V (verbal) and M (motor). In clinical practice all three subscales are reported individually plus the 'Total score', if applicable. A recorded response for each of E, V and M is mandatory. If a response cannot be tested, then the 'Not Applicable' null flavour should be recorded; do not use the 'None' ordinal value to record a missing component. Details about the reason for not being able to test a response can be recorded in the 'Confounding factors' data element. The 'Total score' can be derived as the sum of the recorded eye, motor and verbal response scores. It is not appropriate to report a 'Total score' when one or more components are not testable because the score will be artificially low - in this situation record the EVM profile instead. The three response values are considered separately as well as their sum. The 'EVM profile' can be derived as a concatenation of each of the recorded eye, motor and verbal response scores. For example, E3 V4 M2 represents the conscious state of a subject who opens eyes to speech, utters incomprehensible sounds and has an extensor response to stimulation. The minimum possible 'Total score' value is 3 (equivalent to E1 V1 M1) and the maximum possible is 15 (equivalent to E4 V5 M6). In practical use, Glasgow coma scale is recorded as one component of clinical monitoring, using sequential and repeated point-in-time measurements. Date and time should be recorded for each measurement, as well as any factors that may influence interpretation of changes. Changes in 'Total score' or any E, V or M values may have as much clinical significance as the value recorded initially.
- 7/10/17 - 1 form, 1 itemgroup, 53 items, 3 languages
Itemgroup: openEHR-EHR-INSTRUCTION.medication_order.v1.xml
Derived from www.openehr.org . Use to record all aspects of an order of a medication, vaccine, nutritional product or other therapeutic item for an identified individual. It is intended to be used for any type of medication and related order, whether prescribed by a health professional or available for purchase 'over the counter'. The scope of this medication archetype also includes orders for vaccinations, parenteral fluids or other therapeutic goods, such as bandages, nutritional products or other items that are applied or administered to have a therapeutic effect and which have a common pattern for data recording. This archetype is designed to be used in a number of clinical contexts, including but not limited to: - a record in a clinical consultation (COMPOSITION.encounter); - a written prescription by a physician, dentist, nurse practitioner, or other designated health professional for a medication or nutritional product to be dispensed and administered (within a COMPOSITION.prescription); - an item in a current medication list, prescription or drug chart (within COMPOSITION.medication_list); and - an item in a summary document such as transfer of care (COMPOSITION.transfer_summary) or a referral (COMPOSITION.request). In many cases a medication order will be simple – typically for a single medication item with uncomplicated instructions for dispensing and administration. However this archetype is also designed to allow for more complex therapeutic orders. For example: - a reducing dose of prednisolone over a period of weeks; - titration of insulin, with dosing dependent on test results; - multiple medications prescribed simultaneously as part of a single drug regimen, such as a triple therapy for peptic ulcer; and - intravenous administration of medications or nutrition supplements, including parenteral nutrition. The archetype has therefore been designed to allow for a range of complexity, from: - simple narrative instructions for orders like 'furosemide 40mg two tablets in the morning and one at lunch' to ensure compatibility with existing systems; and - the amount of medication is usually represented in terms of a number and corresponding dose unit, however there can alternatively be a narrative statement to ensure compatibility with existing systems and coverage of all clinical scenarios; through to - structured detail for dose, route and timing to represent a fully computable specification. It has also been designed so that a single medication order structure can represent: - complex sequential medication orders using the same preparation strength to be supported within a single order structure; and - multiple medication orders can be chained in circumstances where different medications or preparations need to be given sequentially. This archetype is also suitable for ordering parenteral fluids, in care settings where it is normal practice to make these 'prescribable' items. In other settings a separate 'parenteral fluid order' may be appropriate. SLOTs containing CLUSTER archetypes have been used to represent some of the content for three reasons: - To ensure a core archetype that can be used for all the above use cases, yet allow flexibility where it is required, for example the ‘Preparation details’ SLOT where additional structured detail can be added. A candidate archetype has been suggested for Medications. It is possible that other CLUSTER archetypes may be required in future for other purposes such as complex parenteral nutrition orders; - to support archetype re-use in situations where the content has been identified as being also used in other clinical contexts, in particular the paired ACTION.medication archetype for recording actual dispensing, administration etc; and - to remove less commonly used content from the core archetype framework. Multiple orders can be represented as separate activities within this single archetype instance to carry tightly bound orders of different medications, for example, H. pylori therapy when this is not prescribed as a single pack. It should be noted that these uses subsume both the FHIR Medication Order and Medication Statement use cases. i.e this archetype is a match for both FHIR resources, used in the appropriate context.
- 7/10/17 - 1 form, 1 itemgroup, 16 items, 2 languages
Itemgroup: openEHR-EHR-OBSERVATION.paced_auditory_serial_addition_test.v1.xml
- 7/9/17 - 1 form, 1 itemgroup, 5 items, 9 languages
Itemgroup: openEHR-EHR-OBSERVATION.height.v1.xml
Derived from www.openehr.org . To be used for recording the actual height or body length of an individual at any point in time. A statement identifying the physical incompleteness of the body can be recorded in the 'Confounding factors' protocol element, if required. This is the usual archetype to be used for a typical measurement of height or body length, independent of the clinical setting. Can also be used for recording an approximation of height or body length measurement in a clinical scenario where it is not possible to measure an accurate height or length - for example, measuring an uncooperative child. This is not modelled explicitly in the archetype as the openEHR Reference model allows the attribute of Approximation for any Quantity data type. At implementation, for example, an application user interface could allow clinicians to select an appropriately labelled check box adjacent to the Height data field to indicate that the recorded height is an approximation, rather than actual. In general, length measurements are recommended for children under 2 years of age and individuals who cannot stand; height measurements for all others. Ideally, height is measured standing on both feet with weight distributed evenly, heels together and both buttocks and heels in contact with a vertical back board; body length is measured in a fully extended, supine position with the pelvis flat, legs extended and feet flexed. Use to record growth and loss of height. This can currently be modelled by constraining the 'any event' to an interval in a template with associated mathematical function of increase or decrease, as appropriate.

Please use this form for feedback, questions and suggestions for improvements.

Fields marked with * are required.

Do you need help on how to use the search function? Please watch the corresponding tutorial video for more details and learn how to use the search function most efficiently.

Watch Tutorial