TEMPLATE Clinical image acquisition and validation NMR (Clinical image acquisition and validation NMR)

TEMPLATE IDClinical image acquisition and validation NMR
ConceptClinical image acquisition and validation NMR
DescriptionRegister the acquisition and subsequent examination of non-mydriatic retinography test.
PurposeRegister the acquisition and subsequent examination of non-mydriatic retinography test.
References
Authorsname: Aitor Eguzkitza; organisation: Universidad Pública de Navarra - Complejo Hospitalario de Navarra; email: aitor.eguzkiza@unavarra.es; date: 2016-07-20
Other Details Languagename: Aitor Eguzkitza; organisation: Universidad Pública de Navarra - Complejo Hospitalario de Navarra; email: aitor.eguzkiza@unavarra.es; date: 2016-07-20
Other Details (Language Independent)
  • MetaDataSet:Sample Set : Template metadata sample set
  • Copyright: © openEHR Foundation
  • Owner: Aitor Eguzkitza, aitor.eguzkiza@unavarra.es
  • Speciality: Ophthalmology
Language useden
Citeable Identifier1013.26.116
Root archetype idopenEHR-EHR-SECTION.clinical_image_acquisition.v0
Clinical image acquisition and validation NMRClinical image acquisition and validation NMR: Manages the acquisition and validation of diagnostic tests based on medical imaging.
Imaging examinationImaging examination: Clinical activity about performing an imaging examination.
Description
Examination nameExamination name: The name of the examination (to be) performed. Coding of the specific procedure with a terminology is preferred, where possible.
Default value: Eye fundus examination
DescriptionDescription: Narrative description about the activity or care pathway step for the identified examination, for example description about the performance and findings from the the examination, the failed attempt or the cancellation of the examination.
Default value: Carry out the funduscopic examination of eyes.
ReasonReason: Reason that the activity or care pathway step for the identified examination was carried out, for example, the reason for the cancellation or suspension of the examination.
  • DR screening
  • Assessment of wet AMD
  • Monitor the progression of chronic glaucoma
Anatomical locationAnatomical location: A physical site on or within the human body.
Body site nameBody site name: Identification of a single physical site either on, or within, the human body.
This data element is the only mandated data point in this archetype and should be used as the primary data point to record an anatomical location with a commonly used name. It is strongly recommended that 'Body site name' be recorded as specifically as is anatomically possible. For example: record 'upper eyelid' rather than recording 'eyelid' with 'upper' as a qualifier; 'fifth rib' rather than 'rib' with a numeric qualifier. Use the other data elements for laterality, aspect, region and anatomical line to provide more detail. This data element should be coded with a terminology capable of triggering decision support, where possible - an appropriate termset for use here could comprise individual concepts or a list of precoordinated terms. Free text should be used only if there is no appropriate terminology available.
Default value: Eye fundus
Specific siteSpecific site: Additional detail using a specific region or a point on, or within, the identified body site.
Use to increase precision of identification of the body site, if required. For example, the upper right quadrant or McBurney's point on the abdominal wall or interphalangeal joint of the great toe. If the 'Body site name' data element uses pre-coordinated terms that include the specific site, then this data element is redundant.
Value set: terminology:Snomed?subset=Subdivision%20of%20retina&language=en-GB
LateralityLaterality: The side of the body on which the identified body site is located.
If the identified body site has no laterality, this data element should not have a value. If the 'Body site name' data element uses pre-coordinated terms that include laterality, then this data element is redundant.
  • Left 
  • Right 
AspectAspect: Qualifying detail about the specific aspect of the identified body site.
Use to increase precision of identification of the body site, if required. Common aspects have been included as a value set, which can be extended over time, plus a free text option. Assumes that the body is being described while in the anatomical position. For example: proximal urethra; plantar aspect of the left thumb. Multiple aspects can also be described, if required, by allowing for 0..2 occurrences. For example: a lesion may be on the left anterior/lateral (ie anterolateral) chest wall. If the 'Body site name' data element uses pre-coordinated terms that include the aspect, then this data element is redundant.
  •  Coded Text
    • Medial 
    • Lateral 
    • Superior 
    • Inferior 
    • Anterior 
    • Posterior 
    • Proximal 
    • Distal 
    • Palmar 
    • Plantar 
    • Mid 
    • Oral 
    • Anal 
  •  Text
Anatomical LineAnatomical Line: Additional detail using theoretical lines drawn through anatomical structures used to provide a consistent reference point on the human body.
Common anatomical lines have been included as a value set, which can be extended over time, plus a free text option. The additional use of this data element allows for recording of the typical position of the heart's apex beat at 5th intercostal space, left side, and mid-clavicular line. If the 'Body site name' data element uses pre-coordinated terms that include anatomical line, then this data element is redundant.
  •  Coded Text
    • Midline 
    • Midaxillary line 
    • Anterior axillary line 
    • Posterior axillary line 
    • Mid-clavicular line 
    • Mid-pupillary line 
    • Mid-scapular line 
  •  Text
DescriptionDescription: Narrative description that can be used to further refine and support the 'Body site name'.
For example: adjacent to the vermilion border; a tattoo covers the bottom half of this area.
Mydriasis applicationMydriasis application: Defines the characteristics of mydriasis procedure when carried out on a patient.
Pupil dilatedPupil dilated: Whether or not the patient’s pupils were pharmacologically dilated for the current acquisition.
Matches to DICOM (0022,000D) attribute.
Degree of dilationDegree of dilation: The degree of the dilation in mm.
Matches to DICOM (0022,000E) attribute.
0..3 mm
Assumed value: 0 mm
Mydriatic delivery methodMydriatic delivery method: The method of delivery if this should be specified (e.g. via a nebuliser or drops).
Mydriatic agentMydriatic agent: Chemical name of the compound used to apply midriasis.
Matches to DICOM (0022,0058) attribute. Values permitted are defined by DICOM standard (PS 3.16) inside the table with Context ID 4208 (Mydriatic agent)
Value set: terminology:Snomed?subset=Mydriatic%20agents&language=en-GB
Medication supply amountMedication supply amount: Details related to the amount of a medication, vaccine or other therapeutic item to be supplied or supplied to the patient, as part of authorisation, dispensing or administration.
Amount descriptionAmount description: A narrative representation of the amount The amount of medication, vaccine or therapeutic good intended to be supplied or actually supplied.
AmountAmount: The amount of medication, vaccine or therapeutic good intended to be supplied or actually supplied.
For example: 1, 1.5, or 0.125.
>=0
UnitsUnits: The dose unit or pack unit associated with the dispense amount.
For example: 'tablets', 'packs', ml'.
Duration of supplyDuration of supply: The period of time for which the medication should be dispensed or for which a suppy was dispensed.
The dispenser is asked to supply sufficient quantity of medication to cover the defined period.
>=P0D
Units:
  • Year
  • Month
  • Week
  • Day
  • Second
CommentComment: Additional narrative about the activity or care pathway step not captured in other fields.
Protocol
Start date/timeStart date/time: The start date and/or time for the procedure. This will indicate the scheduled date/time when recorded against the 'Appointment scheduled' care pathway step or the actual Start date/time in the 'Examination performed' step.
Fundoscopic examination of eyesFundoscopic examination of eyes: Record of clinical findings on fundoscopy of eyes
Data
Any eventAny event: *
Data
Clinical DescriptionClinical Description: Descriptive overview of examination findings
Test ResultTest Result: Details of the funduscopic examination test result for each eye.
SideSide: Determines the eye on which the test was performed.Matches to DICOM Laterality (0020,0060) attribute.
  • Left eye 
  • Right eye 
Acquisition detailsAcquisition details: Details about acquisition obtained during the examination of eye fundus
Red reflexRed reflex: True if Red Reflex is present
Assumed value: false
Small pupilSmall pupil: True if during the acquisition, pupil diameter is smaller than normal (3,3mm)
Assumed value: false
High refractionHigh refraction: True if the refraction of the eye exceeds the range from -12D to +15D
Assumed value: false
Cataract artifactCataract artifact: True if cataract obstructs the visualization of eye fundus
Assumed value: false
Shadow artifactShadow artifact: True if shadow artifact is present on the border of the image
Assumed value: false
Uncooperative patientUncooperative patient: True if patient doesn't collaborate during the image acquisition
Assumed value: false
OthersOthers: Other details identified during the acquisition which may affect the results from reviewing the test
Value set: terminology:Snomed?subset=Complications%20on%20ophthalmic%20image%20acquisition&language=en-GB
VisualizationVisualization: Details about image quality related to ease of visualization of structures on eye fundus
QualityQuality: Levels quantifying the quality of each acquisition, based in the ease to visualize the structures on the eye fundus
  • 1: Quality inadequate for any diagnostic purpose 
  • 2: Unable to exclude all emergent findings 
  • 3: Only able to exclude emergent findings 
  • 4: Quality not ideal, but is possible to exclude subtle findings 
  • 5: Ideal quality 
CommentComment: Comment, especially if not fully visualised
Structural descriptionStructural description: General description of the structures in the eye fundus
Optic DiscOptic Disc: Description of optic disc
MaculaMacula: Description of macula
Retinal arteriesRetinal arteries: Description of retinal arteries
Retinal veinsRetinal veins: Description of retinal veins
Retinal backgroundRetinal background: Description of retinal background
VitreousVitreous: Description of vitreous humour
Clinical resultsClinical results: Information of diagnostic interest obtained in the test
Other findingsOther findings: Narrative description of clinical findings not considered in the SLOT
State
Mydriatic usedMydriatic used: True if mydriatic is used
Assumed value: false
Protocol
MethodMethod: Method chosen to perform the funduscopic examination
  • Direct 
  • Indirect 
  • Contact lens biomicroscopy 
  • Non-contact lens biomicroscopy 
  • Mydriatic retinography 
  • Non-mydriatic retinography 
  • Angiography 
Medical DeviceMedical Device: An instrument, apparatus, implant, material or similar, used in the provision of healthcare. In this context, a medical device includes a broad range of devices which act through a variety of physical, mechanical, thermal or similar means but specifically excludes devices which act through medicinal means such as pharmacological, metabolic or immunological methods. The scope is inclusive of disposable devices as well as durable or persisting devices that require tracking, maintenance activities or regular calibration, recognising that each type of device has specific data recording requirements.
Device nameDevice name: Identification of the medical device, preferably by a common name, a formal fully descriptive name or, if required, by class or category of device.
This data element will capture the term, phrase or category used in clinical practice. For example: <brand name><machine> (XYZ Audiometer); <size> <brand name> <intravenous catheter> (14G Jelco IV catheter); or <brand name/type> <implant>. Coding with a terminology is desirable, where possible, although this may be local and depending on local supplies available.
Value set: terminology:Snomed?subset=Ophthalmic%20photography%20devices&language=en-GB
TypeType: The category or kind of device.
Not applicable if a category is already recorded in 'Device name'. Example: if the 'Device' is named as a 'urinary catheter'; the 'Type' may be recorded as 'indwelling' or 'condom'.Coding with a terminology is desirable, where possible. This may include use of GTIN or EAN numbers.
DescriptionDescription: Narrative description of the medical device.
Unique device identifier (UDI)Unique device identifier (UDI): A numeric or alphanumeric string that is associated with this device within a given system.
Often fixed to the device as a barcode.
ManufacturerManufacturer: Name of manufacturer.
Date of manufactureDate of manufacture: Date the device was manufactured.
Serial numberSerial number: Number assigned by the manufacturer which can be found on the device, and should be specific to each device., its label, or accompanying packaging.
Catalogue numberCatalogue number: The exact number assigned by the manufacturer, as it appears in the manufacturer's catalogue, device labeling, or accompanying packaging.
Model numberModel number: The exact model number assigned by the manufacturer and found on the device label or accompanying packaging.
Batch/Lot numberBatch/Lot number: The number assigned by the manufacturer which identifies a group of items manufactured at the same time, usually found on the label or packaging material.
Software versionSoftware version: Identification of the version of software being used in the medical device.
When the medical device is an actual software application, record the version of the software using this data element. When the medical device has multiple software applications embedded within it, record each software component in a separate CLUSTER archetype within the Components SLOT - either as a nested instance of another CLUSTER.device archetype or using a CLUSTER archetype designed specifically for recording software details (but not yet available at time of this archetype development).
Date of expiryDate of expiry: Date after which the device/product is no longer fit for use, usually found on the device itself or printed on the accompanying packaging.
This date usually applies only to single use or disposable devices.
Other identifierOther identifier: Unspecified identifier, which can be further specified in a template or at run time.
Coding of the name of the identifier with a coding system is desirable, if available.
Medical device detailsMedical device details: Specific details that relate to asset management for any medical device that is designed for more than a single use.
Organisation identifierOrganisation identifier: Organisation identifier for device.
May be a text string or an IEEE EUI-64 identifier.
  •  Text
  •  Identifier
OwnerOwner: Organisation responsible for the medical device.
LocationLocation: Physical location where device is kept.
Network addressNetwork address: Network address to contact the device.
Part numberPart number: The part number of the device.
Manufacturer model nameManufacturer model name: HL7 CDA compatible representation of device manufacture details.
May be a simple string or contain simple markup e.g. for Continua PHMR reports: "Pulse Master 2000||584216|69854|2.1|1.1|1.0|" repesenting Model, Unspecified, SerialNumber, PartNumber, HardwareRevision, SoftwareRevision, ProtocolRevision, and ProdSpecGMDN.
Hardware revisionHardware revision: The hardware revision number.
Protocol revisionProtocol revision: The protocol revision number.
Sampling frequencySampling frequency: The sampling frequency limits of the device.
  •  Text
  •  Quantity
RangeRange: The range limits of the device.
  •  Text
  •  Interval of Quantity
AccuracyAccuracy: The accuracy limits of the device.
  •  Text
  •  Quantity
ResolutionResolution: The resolution limits of the device.
  •  Text
  •  Quantity
Regulatory statusRegulatory status: Whether device is regulated or otherwise.
Date last cleaned/sterilizedDate last cleaned/sterilized: Date the device was last cleaned or sterilized.
Date last calibratedDate last calibrated: Date the device was last calibrated.
Date last servicedDate last serviced: The date the device was last serviced.
FormulaeFormulae: Details about formulae or algorithms used by the device in order to generate results/output.
Formula nameFormula name: Data element which is calculated or derived.
FormulaFormula: Formula used to calculate or derive the Calculated field.
CommentComment: Additional narrative about the device not captured in other fields.
Field angleField angle: Describes the optical acceptance angle of the lens used during the test
  • 30º 
  • 45º 
  • 60º 
  • 100º 
  • 200º 
AttemptsAttempts: Number of attempts before obtaining the acquisition (doesn't compute if test is repeated by a specific recognized technical failure)
1..3
(Subdivision of the retina)(Subdivision of the retina): Subdivision of the retina identifying eye fundus image locations
(ETRDS fields)(ETRDS fields): Subdivision of the retina based on Diabetic Retinopathy Study fields
  • Study field 1 
  • Study field 2 
  • Study field 3 
  • Study field 4 
  • Study field 5 
  • Study field 6 
  • Study field 7 
Mosaic and peripheralsMosaic and peripherals: Division of the retina in quadrants + mosaic obtained from the combination of them
  • Mosaic 
  • Central 
  • Nasal 
  • Temporal 
  • Superior 
  • Inferior 
Other contributorsJose Andonegui, Complejo hospitalario de Navarra (CHN), jose.andonegui.navarro@cfnavarra.es; Luis Serrano, Universidad Pública de Navarra (UPNA), lserrano@unavarra.es; Jesús D. Trigo, Universidad Pública de Navarra (UPNA), jesusdaniel.trigo@unavarra.es