TEMPLATE Annotations variety AHSsg via rest (Annotations variety AHSsg via rest)

Type: openEHR TEMPLATE
Purpose: To test advanced annotations for AHS, especially in review
Use: Use to demo.
Misuse: To for anything else apart from testing.

Available formats: ADL XML

TEMPLATE IDAnnotations variety AHSsg via rest
ConceptAnnotations variety AHSsg via rest
DescriptionTo test advanced annotations for AHS, especially in review
UseUse to demo.
MisuseTo for anything else apart from testing.
PurposeTo test advanced annotations for AHS, especially in review
References
Other Details (Language Independent)
  • MetaDataSet:Sample Set : Template metadata sample set
Keywordstest1; test annotations
Language useden
Citeable Identifier1013.26.940
Root archetype idopenEHR-EHR-CLUSTER.device_details.v1
Device detailsDevice details: Additional details that relate to safety and quality issues for ongoing and repeated use of any device.
Organisation identifierOrganisation identifier: Organisation identifier for device. May be a text string or an IEEE EUI-64 identifier.
  •  Text
  •  Identifier
ModelModel: The model of 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.
Software nameSoftware name: Software name - for compatibility with CDA POCD_MT000040.
Software revisionSoftware revision: The software 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

Annotations

  • Authors Note TEXT ONLY: Just a test annotation without any special formatting here.
  • Image Directly Included In The Template:
  • Example With Formatting:

    My text!Needs to be searchable!

  • Example With Html List:
    • My text!
    • My text!
      • Just a list!
  • Example With Numbered List:
    1. My text!
    2. My text!
      3. And a numbered list!
  • Example With An Image From A Remote URL.: I18n Guy, your I18n advisor
  • Example With The OpenEHR Logo From A Remote URL.: openEHR logo
  • Example With An Image From A Resource Centre: A local image
  • Example With An Html Fragment From A Resource Centre:
  • Clinical Knowledge Topic.Analytics:

    Priority

    • 1 - Criteria: * Required to meet legislation, accreditation, project or governance mandated timelines * Existing knowledge/guidance contains error that could cause patient harm * New requirement to prevent patient harm
    • 2 - Criteria: * Required change or new knowledge/guidance that does not cause immediate patient safety issue * Significant usability issue * Missing elements/required changes that could improve patient outcomes or usability
    • 3 - Criteria: * Required change or new knowledge/guidance that will aid in usability * Minor change/issue. No patient risk or major usability issue

    Affects Version(s) - AKA "Release"

    • Release 1 = Jan - March
    • Release 2 = April - June
    • Release 3 = July - Sept
    • Release 4 = Oct - Dec

    Date Fields

    • Target Start Date = Enter the date the work is scheduled to start. This is a static field - Do not change the value once entered.
    • Target End Date = Enter the date the work is scheduled to be completed. This is a static field - Do not change the value once entered.
    • Release Date = This is a dynamic field of the date the deliverable is expected to be sent for publication.
    • Resolved Date = This is not a field to fill out in JIRA. Automatically displays when ticket is closed. Ticket to be closed when content is available to the public and all work is done.
  • Clinical Knowledge Topic.Appendix A:
    Phase % complete range % complete value when phase complete
    Pre-planning (Intake) 0-15% 15%
    Planning 15-25% 25%
    Development 25-75% 75% (for Knowledge Topics - set to 50% once CKT is sent for CSS/Colleague Review)
    Review and approval & Communication 75-95% 95%
    Dissemination 95-100% 100%
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.
Additional informationAdditional information: Addtional device specification information.
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.