AU Base Implementation Guide
4.2.2-ci-build - CI Build Australia flag

AU Base Implementation Guide, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 4.2.2-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7au/au-fhir-base/ and changes regularly. See the Directory of published versions

Resource Profile: AU Base Diagnostic Result

Official URL: http://hl7.org.au/fhir/StructureDefinition/au-diagnosticresult Version: 4.2.2-ci-build
Standards status: Trial-use Maturity Level: 1 Computable Name: AUBaseDiagnosticResult

Copyright/Legal: HL7 Australia© 2018+; Licensed Under Creative Commons No Rights Reserved.

This profile defines an observation structure to represent a diagnostic investigation result issued by a diagnostic service provider in an Australian context. This profile may be used to represent a specialist or other diagnostic (not imaging or pathology) observation including results of audiology studies, sleep studies or speech pathology. The observation may represent the result of a simple investigation or it may group the set of results of a multi-modality procedure or multi-test study / panel.

Usage Notes

Profile specific implementation guidance:

  • The bodySite extension may be suitable for use where
    • body site is not implicit in the code found in Observation.code and
    • body site information is to be handled as a separate resource (e.g. to identify and track separately) instead of an inline coded element in Observation.bodySite.
  • See the AU Base Pathology Result profile for guidance on representing the result of a pathology test.
  • See the AU Base Diagnostic Imaging Result profile for guidance on representing the result of a radiology examination or an imaging intensive diagnostic investigation.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Observation

NameFlagsCard.TypeDescription & Constraintsdoco
.. Observation C 0..* Observation A diagnostic result observation in an Australian healthcare context
inv-obs-0: A diagnostic result shall at least have value or data absent reason or a child observation with a value or data absent reason
... Slices for extension 0..* Extension Extension
Slice: Unordered, Open by value:url
.... bodySite 0..1 Reference(BodyStructure) Target anatomic location or structure
URL: http://hl7.org/fhir/StructureDefinition/bodySite
... category 1..* CodeableConcept Diagnostic service section
Binding: DiagnosticServiceSectionCodes (preferred)
... code 1..1 CodeableConcept Diagnostic procedure
Binding: Evaluation Procedure . (example)
... effective[x] 1..1 dateTime, Period, Timing, instant Clinically relevant time/time-period for observation
... value[x] C 0..1 Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period Actual result
... dataAbsentReason C 0..1 CodeableConcept Why the result is missing
... hasMember C 0..* Reference(AU Base Diagnostic Result | AU Base Diagnostic Imaging Result | AU Base Pathology Result) Individual examinations in a group or study series
... component
.... value[x] C 0..1 Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period Actual component result
.... dataAbsentReason C 0..1 CodeableConcept Why the component result is missing

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSetURI
Observation.categorypreferredDiagnosticServiceSectionCodes
http://hl7.org/fhir/ValueSet/diagnostic-service-sections
from the FHIR Standard
Observation.codeexampleEvaluationProcedure .
https://healthterminologies.gov.au/fhir/ValueSet/evaluation-procedure-1

Constraints

IdGradePath(s)DetailsRequirements
inv-obs-0errorObservationA diagnostic result shall at least have value or data absent reason or a child observation with a value or data absent reason
: value.exists() or dataAbsentReason.exists() or hasMember.exists() or component.value.exists() or component.dataAbsentReason.exists()

 

Other representations of profile: CSV, Excel, Schematron