4. AOE Observations - Healthedata1/OO-on-FHIR-Micro-Profile GitHub Wiki

This Profile on Observation defines the "Ask at Order (AOE)" observations for a culture.

AOEs can result in a variety of observations including coded, numeric and date responses. The Terminology refers to an initial valueset drafted by the [EDOS}(http://www.hl7.org/documentcenter/public/standards/dstu/V2_IG_LTCF_R2_DSTU_R2_2015SEP.pdf) workgroup. The pattern is assumed to be one to many simple observations for each AOE. The category 'AOE' is required for these observations in addtition to the micro and lab categories.

Based on DAF-Core/US-Core plus additional USlab (LRI) and US-Core Micro Report constraints (in italics):

Each AOE Observation must include:

  1. a status
  2. a category code of ‘laboratory’
  • micro category code as translation
  1. a category code of 'AOE' ( this is currently implemented as a translation - THIS IS WRONG BUT Currently US_core observation is limited to 1..1 - need to update the US-Core before can repeat - made a ballot comment to change this)
  2. a LOINC code, if available, which tells you what is being measured
  3. performing organization
  4. a patient
  5. a result value and, if the result value is a numeric quantity, a standard UCUM unit

Each AOE must include: must support:

(stuff from LRI OBX and OBR)

  1. an identifier (Filler/Placer) - Discuss whether this is a must support - not an LRI requirement
  2. a time indicating when the specimen was collected - discuss if needed for AOEs
  3. a time indicating when the measurement was reported - discuss if needed for AOEs

Terminology considerations ( note need help from community to work these out)

For Observation.code - extensible binding to list of AOEs from EDOS

NOTE: Specific AOEs may have specific answer lists as well.

View US-Core AOE StructureDefinition