Use to record information about the activities required to carry out the fitting of a non-invasive device to an individual, including the planning, scheduling, performance, suspension, cancellation, documentation and completion. This is done by the recording of data against specific activities, as defined by the 'Pathway' careflow steps in this archetype.
The scope of this archetype encompasses activities for a broad range of devices. Examples include, but are not limited to:
- hearing aid;
- orthotics; and eyeglasses.
Additional structured and detailed information about the device fitting can be captured using purpose-specific archetypes inserted into the 'Fitting detail' slot, where required.
Timings related to a fitting can be managed in one of two ways:
- Using the reference model - the time for performance of any pathway step will use the ACTION time attribute for each step.
- Archetyped data elements:
--- the 'Scheduled date/time' data element is intended to record the time when the fitting is planned. Note: the corresponding ACTION time attribute for the Scheduled pathway step will record the time that the fitting was scheduled into a system, not the intended date/time on which the fitting is intended to be carried out; and
--- the 'Final end date/time' is intended to record the precise time when the fitting was ended. It can be used to document the complex fittings with multiple components. Note: the corresponding ACTION time attribute for the 'fitting performed' will document the time each component performed was commenced. This 'Final end date/time' data element will record the date/time of the final active component of the fitting. This will enable a full duration of the active fitting to be calculated.
Within the context of a fitting consultation, this archetype will be used to record only what was done during the fitting. Separate archetypes will be used to record the other required components such as test resutls and plans for follow up.
Within the context of a device summary record, this archetype may be used to represent each fitting that has been performed and a summary EVALUATION archetype can represent basic information about each previous fitting - for example EVALUATION.assisted_hearing_summary.
In most situations, it is likely that there will be a formal order for a fitting using a corresponding INSTRUCTION.request, or similar, archetype. This ACTION archetype can then be used to record the workflow of when and how the order has been carried out.
Recording information using this ACTION archetype indicates that some sort of activity has actually occurred; this will usually be the fitting itself but may be a failed attempt or another activity such as postponing the fitting.
Please note that in the openEHR Reference Model there is a 'Time' attribute, which is intended to record the date and time at which each pathway step of the Action was performed. This is the attribute to use to record the start of the fitting (using the 'Fitting performed' pathway step) or the time that the fitting was completed (using the 'Fitting completed' pathway step).
Organisation: Ocean Informatics, Australia
Email: heather.leslie@oceaninformatics.com
Date originally authored: 2007-03-12
Organisation: Ocean Informatics, Australia
Email: heather.leslie@oceaninformatics.com
Date originally authored: 2007-03-12
- Licence: This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/.
- Custodian Organisation: Ocean Informatics
- References: fitting, Draft Archetype [Internet]. National eHealth Transition Authority, Australia, NEHTA Clinical Knowledge Manager [cited: 2015-03-21]. Available from: http://dcm.nehta.org.au/ckm/#showArchetype_1013.1.936.
- Current Contact: Heather Leslie, Ocean Informatics, heather.leslie@oceaninformatics.com
- Original Namespace: com.oceaninformatics
- Original Publisher: Ocean Informatics
- Custodian Namespace: com.oceaninformatics
- MD5-CAM-1.0.1: C660959C82AEB9E6E76C8B5ACADCD9BB
- Build Uid: 1e83293d-81cd-4aae-8ccc-c856e5af8bd6
- Revision: 0.0.1-alpha
Current state: initial
Current state: initial
Current state: postponed
Current state: cancelled
Current state: scheduled
Current state: active
Current state: active
Current state: suspended
Current state: aborted
Current state: completed
For example: local information requirements or additional metadata to align with FHIR or CIMI equivalents.
Include:
All not explicitly excluded archetypes
Choice of:
Text
Identifier
Include:
All not explicitly excluded archetypes
Choice of:
- Text
- Identifier
Include:
All not explicitly excluded archetypes
Coding of the specific fitting with a terminology is preferred, where possible.
For example: description about the performance and findings from the the fitting, the aborted attempt or the cancellation of the fitting.
Coding with a terminology is preferred, where possible.
Occurrences for this data element are unbounded to allow for clinical scenarios such as removing multiple skin lesions in different places, but where all of the other attributes are identical. Use this data element to record simple terms or precoordinated anatomical locations. If the requirements for recording the anatomical location are determined at run-time by the application or require more complex modelling such as relative locations then use the CLUSTER.anatomical_location or CLUSTER.relative_location within the 'fitting detail' SLOT in this archetype. If the anatomical location is included in the 'fitting name' via precoordinated codes, this data element becomes redundant.
Use to capture detailed, structured information about anatomical location, method & technique, equipment used, devices implanted, results, findings etc.
Include:
openEHR-EHR-CLUSTER.device.v1 and specialisations or
openEHR-EHR-CLUSTER.anatomical_
openEHR-EHR-CLUSTER.anatomical_
openEHR-EHR-CLUSTER.anatomical_
Coding with a terminology is preferred, where possible. For example: successful fitting or description of any problems encountered.
Only for use in association with the 'fitting scheduled' pathway step.
Only for use in association with the 'fitting performed' pathway step, and in situations where the fitting is repeated on multiple occasions before being completed or there are multiple components to the whole fitting. This may be the same as the RM time attribute for the 'fitting completed' pathway step.
Include:
openEHR-EHR-CLUSTER.multimedia.v1 and specialisations
For example: the reason for the cancellation or suspension of the fitting.
Vebjoern Arntzen, Oslo university hospital, Norway
Vebjørn Arntzen, Oslo universitetssykehus HF, Norway
Koray Atalag, University of Auckland, New Zealand
Silje Ljosland Bakke, Bergen Hospital Trust, Norway (openEHR Editor)
Kari Beate Engseth, Finnmarkssykehuset HF + Klinikk Kirkenes, Norway
Lars Bitsch-Larsen, Haukeland University hospital, Norway
Diego Bosca, IBIME group, Spain
Rong Chen, Cambio Healthcare Systems, Sweden
Stephen Chu, NEHTA, Australia (Editor)
Lisbeth Dahlhaug, Helse Midt - Norge IT, Norway
David Evans, Queensland Health, Australia
Shahla Foozonkhah, Ocean Informatics, Australia
Einar Fosse, National Centre for Integrated Care and Telemedicine, Norway
Sebastian Garde, Ocean Informatics, Germany
Jacquie Garton-Smith, Royal Perth Hospital and DoHWA, Australia
Andrew Goodchild, NEHTA, Australia
Heather Grain, Llewelyn Grain Informatics, Australia
Megan Hawkins, Mater Health Services, Australia
Sam Heard, Ocean Informatics, Australia
Andreas Hering, Helse Bergen HF, Haukeland universitetssjukehus, Norway
Anca Heyd, DIPS ASA, Norway
Lars Karlsen, DIPS ASA, Norway
Mary Kelaher, NEHTA, Australia
Shinji Kobayashi, Kyoto University, Japan
Sabine Leh, Haukeland University Hospital, Department of Pathology, Norway
Heather Leslie, Ocean Informatics, Australia (openEHR Editor)
Hugh Leslie, Ocean Informatics, Australia
Hallvard Lærum, Oslo University Hospital, Norway
Mike Martyn, The Hobart Anaesthetic Group, Australia
Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (openEHR Editor)
Chris Mitchell, RACGP, Australia
Lars Morgan Karlsen, DIPS ASA, Norway
Stewart Morrison, NEHTA, Australia
Bjoern Naess, DIPS ASA, Norway
Bjørn Næss, DIPS ASA, Norway
Andrej Orel, Marand d.o.o., Slovenia
Michael Osborne, Mater Health Services, Australia
Anne Pauline Anderssen, Helse Nord RHF, Norway
Chris Pearce, Melbourne East GP Network, Australia
Rune Pedersen, Universitetssykehuset i Nord Norge, Norway
Jussara Rotzsch, UNB, Brazil
Peter Scott, Australia
Elizabeth Stanick, Hobart Anaesthetic Group, Australia
Norwegian Review Summary, Nasjonal IKT, Norway
John Taylor, NEHTA, Australia
Rowan Thomas, St. Vincent's Hospital Melbourne, Australia
John Tore Valand, Haukeland Universitetssjukehus, Norway (Editor)
Richard Townley-O'Neill, NEHTA, Australia
- Russian: Art Latyp; Латыпов Артур, RusBITech; РусБИТех, Москва, hmm
- Norwegian Bokmal: John Tore Valand / Silje Ljosland Bakke, Helse Bergen HF
- Portuguese (Brazil): Thiago F. F. Dias, FMRP-USP
- Arabic (Syria): Mona Saleh
- Slovenian, Slovene: Uroš Rajkovič, Biljana Prinčič, Slovenia