AU Core Implementation Guide
0.4.1-preview - Preview
AU Core Implementation Guide
0.4.1-preview - Preview
This page is part of the AU Core (v0.4.1-preview: QA Preview) based on FHIR (HL7® FHIR® Standard) R4. . For a full list of available versions, see the Directory of published versions
| Official URL: http://hl7.org.au/fhir/core/StructureDefinition/au-core-resprate | Version: 0.4.1-preview | |||
| Standards status: Draft | Maturity Level: 1 | Computable Name: AUCoreRespirationRate | ||
Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License. HL7 Australia© 2022+; Licensed Under Creative Commons No Rights Reserved. |
||||
This profile sets minimum expectations for an Observation resource to record, search, and fetch respiration rate observations with standard coding and units of measure. It is based on the FHIR Respiratory Rate Profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets that SHALL be present in the Observation resource when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.
The following are supported usage scenarios for this profile:
A resource conforming to this profile is conformant to:
Conformance in reverse is not guaranteed, i.e. a resource conforming to International Patient Access, International Patient Summary, or US Core MAY NOT conform to AU Core.
Observation.category provides an efficient way of supporting system interactions, e.g. restricting searches. Implementers need to understand that data categorisation is somewhat subjective. The categorisation applied by the source may not align with a receiver’s expectations.Usage:
Description of Profiles, Differentials, Snapshots and how the different presentations work.
This structure is derived from observation-resprate
| Name | Flags | Card. | Type | Description & Constraints | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
  Observation |
C | 0..* | observation-resprate | Respiration rate au-core-obs-02: At least value or data absent reason shall be present | ||||||
  status |
O | 1..1 | code | registered | preliminary | final | amended +
| ||||||
| category |
O | 1..* | CodeableConcept | Classification of type of observation
| ||||||
  Slices for category |
Content/Rules for all slices | |||||||||
   category:VSCat |
O | 1..1 | CodeableConcept | Classification of type of observation
| ||||||
  coding |
O | 1..* | Coding | Code defined by a terminology system
| ||||||
| system |
O | 1..1 | uri | Identity of the terminology system
| ||||||
 code |
O | 1..1 | code | Symbol in syntax defined by the system
| ||||||
| code |
O | 1..1 | CodeableConcept | Respiratory Rate
| ||||||
| coding |
2..* | Coding | Code defined by a terminology system | |||||||
 Slices for coding |
Content/Rules for all slices | |||||||||
| coding:snomedRespRateCode |
1..1 | Coding | SNOMED CT Respiration Rate | |||||||
 system |
1..1 | uri | Identity of the terminology system Fixed Value: http://snomed.info/sct | |||||||
 code |
1..1 | code | Symbol in syntax defined by the system Fixed Value: 86290005 | |||||||
 subject |
O | 1..1 | Reference(AU Core Patient) | Who and/or what the observation is about
| ||||||
 effective[x] |
OC | 1..1 | dateTime | Date, and optionally time, the observation was performed au-core-obs-01: Date shall be at least to day
| ||||||
| valueQuantity |
OC | 0..1 | Quantity | Respiration rate
| ||||||
| value |
O | 1..1 | decimal | Numerical value (with implicit precision)
| ||||||
| unit |
O | 1..1 | string | Unit representation
| ||||||
| system |
O | 1..1 | uri | System that defines coded unit form
| ||||||
| code |
O | 1..1 | code | Coded responses from the common UCUM units for vital signs value set.
| ||||||
| dataAbsentReason |
OC | 0..1 | CodeableConcept | Why the result is missing
| ||||||
| bodySite |
C | 0..1 | CodeableConcept | Observed body part Binding: Body Site  (preferred)au-core-obs-04: If a coded body site is provided, at least one code shall be from SNOMED CT | ||||||
| component |
O | 0..* | BackboneElement | Used when reporting systolic and diastolic blood pressure.
| ||||||
| code |
O | 1..1 | CodeableConcept | Type of component observation (code / type)
| ||||||
| value[x] |
O | 0..1 | Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Vital Sign Value recorded with UCUM
| ||||||
| dataAbsentReason |
O | 0..1 | CodeableConcept | Why the component result is missing
| ||||||
| Documentation for this format | ||||||||||
| Path | Conformance | ValueSet | URI |
| Observation.bodySite | preferred | BodySite https://healthterminologies.gov.au/fhir/ValueSet/body-site-1 |
| Id | Grade | Path(s) | Details | Requirements |
| au-core-obs-01 | error | Observation.effective[x] | Date shall be at least to day : $this is DateTime implies $this.toString().length() >= 10 | |
| au-core-obs-02 | error | Observation | At least value or data absent reason shall be present : dataAbsentReason.exists() or value.exists() | |
| au-core-obs-04 | error | Observation.bodySite | If a coded body site is provided, at least one code shall be from SNOMED CT : coding.exists() implies coding.where(system='http://snomed.info/sct').exists() |
Other representations of profile: CSV, Excel, Schematron
Below is an overview of the mandatory and optional search parameters and combined search parameters. See the AU Core CapabilityStatements for a complete list of supported RESTful interactions for this IG.
FHIR search operations are described here and the syntax used to describe AU Core interactions is defined here.
Any search parameter defined in FHIR may be ‘allowed’ by the system unless explicitly marked as “SHALL NOT”. A few items are marked as MAY in this implementation guide to highlight their potential relevance.
| Parameter(s) | Conformance | Type(s) | Requirements (when used alone or in combination) |
|---|---|---|---|
| patient | SHALL | reference |
The requester SHALL provide at least an id value and MAY provide both the Type and id values. The responder SHALL support both. |
| patient+category | SHALL | reference+token |
|
| patient+category+date | SHALL | reference+token+date |
|
| patient+code | SHALL | reference+token |
|
| patient+category+status | SHOULD | reference+token+token |
|
| patient+code+date | SHOULD | reference+token+date |
|
| patient.identifier | SHOULD | reference.token |
The requester SHALL provide both the system and code values. The responder SHALL support both. The requester SHOULD support search using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. The responder SHOULD support search using the using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. |
| category | MAY | token |
The requester SHALL provide at least a code value and MAY provide both the system and code values. The responder SHALL support both. The requester SHALL support search using the 'vital-signs' category defined in each profile. The responder SHALL support search using the 'vital-signs' category defined in each profile. |
| code | MAY | token |
The requester SHALL provide at least a code value and MAY provide both the system and code values. The responder SHALL support both. The requester SHALL support search using the LOINC codes defined in each profile. The responder SHALL support search using the LOINC codes defined in each profile. |
| date | MAY | date |
A requester SHALL provide a value precise to the second + time offset. A responder SHALL support a value precise to the second + time offset. |
| status | MAY | token |
The requester SHALL provide at least a code value and MAY provide both the system and code values. The responder SHALL support both. |
The following search parameters and search parameter combinations SHALL be supported:
patient search parameter:
patient.identifier (e.g. patient.identifier=[system|][code])GET [base]/Observation?patient={Type/}[id] or optionally GET [base]/Observation?patient.identifier=[system|][code]
Example:
Implementation Notes: Fetches a bundle of all Observation resources for the specified patient (how to search by reference and how to search by token)
patient and category search parameters:
patient.identifier (e.g. patient.identifier=[system|][code])GET [base]/Observation?patient={Type/}[id]&category=vital-signs
Example:
Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and category (how to search by reference and how to search by token)
patient and category and date search parameters:
patient.identifier (e.g. patient.identifier=[system|][code])date comparators: gt,lt,ge,ledate (e.g.date=[date]&date=[date]]&...)GET [base]/Observation?patient={Type/}[id]&category=vital-signs&date={gt|lt|ge|le}[date]{&date={gt|lt|ge|le}[date]&...}
Example:
Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and date and a category code = vital-signs (how to search by reference and how to search by token and how to search by date)
patient and code search parameters:
patient.identifier (e.g. patient.identifier=[system|][code])code (e.g.code={system|}[code],{system|}[code],...)GET [base]/Observation?patient={Type/}[id]&code={system|}[code]{,{system|}[code],...}
Example:
Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and observation code(s). The Observation code parameter searches Observation.code only. (how to search by reference and how to search by token)
The following search parameters and search parameter combinations SHOULD be supported:
patient and category and status search parameters:
patient.identifier (e.g. patient.identifier=[system|][code])status (e.g.status={system|}[code],{system|}[code],...)GET [base]/Observation?patient={Type/}[id]&category=vital-signs&status={system|}[code]{,{system|}[code],...}
Example:
Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and category and status (how to search by reference and how to search by token)
patient and code and date search parameters:
patient.identifier (e.g. patient.identifier=[system|][code]code (e.g.code={system|}[code],{system|}[code],...)date comparators: gt,lt,ge,ledate (e.g.date=[date]&date=[date]]&...)GET [base]/Observation?patient={Type/}[id]&code={system|}[code]{,{system|}[code],...}&date={gt|lt|ge|le}[date]{&date={gt|lt|ge|le}[date]&...}
Example:
Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and date and observation code(s) (how to search by reference and how to search by token and how to search by date)
IG © 2022+ HL7 Australia. Package hl7.fhir.au.core#0.4.1-preview based on FHIR 4.0.1. Generated 2024-07-18
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change