AU Core Implementation Guide
0.2.1-preview - Preview Australia flag

This page is part of the Australian Core IG (v0.2.1-preview: AU Core) based on FHIR R4. For a full list of available versions, see the Directory of published versions

Resource Profile: AU Core Encounter

Official URL: http://hl7.org.au/fhir/core/StructureDefinition/au-core-encounter Version: 0.2.1-preview
Standards status: Draft Maturity Level: 0 Computable Name: AUCoreEncounter

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 Encounter resource to record, search, and fetch basic encounter information for a patient. It is based on the AU Base Encounter profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets that SHALL be present in the Encounter when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.

Usage scenarios

The following are supported usage scenarios for this profile:

  • Query for a specific patient encounter
  • Query for all patient encounters
  • Record or update a patient encounter

Comparison with other national and international specifications

A resource conforming to this profile:

No equivalent International Patient Access or International Patient Summary profile.

Conformance in reverse is not guaranteed, i.e. a resource conforming to US Core MAY NOT conform to AU Core.

Profile specific implementation guidance

  • The use of coding can vary significantly across systems, client applications need to understand that they may encounter codes they do not recognise and be prepared to handle those resources appropriately. Servers SHOULD populate Encounter.code.text and/or Encounter.code.coding.display so that client applications can at least display the condition even if the client application does not recognise the code supplied.
  • The Encounter resource can represent a reason as a code with Encounter.reasonCode, or a reference with Encounter.reasonReference to a Condition or other resource.
    • Although both are marked as must support, servers are not required to support both a code and a reference, but they SHALL support at least one of these elements
    • A client application SHALL support both elements

Usage:

Formal Views of Profile Content

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

This structure is derived from AUBaseEncounter

NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..*AUBaseEncounterAn encounter in an Australian healthcare context
... extension:encounterDescription S0..1EncounterDescriptionDescription, overview or summary of an encounter
... identifier S0..*IdentifierIdentifier(s) by which this encounter is known
... status S1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
... type S0..*CodeableConceptSpecific type of encounter
Binding: https://healthterminologies.gov.au/fhir/ValueSet/encounter-type-1 (preferred)
... serviceType S0..1CodeableConceptSpecific type of service
Binding: https://healthterminologies.gov.au/fhir/ValueSet/service-type-1 (preferred)
... subject S1..1Reference(AU Core Patient)The patient or group present at the encounter
... participant S0..*BackboneElementList of participants involved in the encounter
.... type S0..*CodeableConceptRole of participant in encounter
.... individual S0..1Reference(AU Core Practitioner | AU Core PractitionerRole | AU Core RelatedPerson)Persons involved in the encounter other than the patient
... period S1..1PeriodThe start and end time of the encounter
... reasonCode S0..*CodeableConceptCoded reason the encounter takes place
... reasonReference[x] S0..*Reference(AU Core Condition | AU Core Observation | AU Core Procedure)Reason the encounter takes place (reference)
... hospitalization S0..1BackboneElementDetails about the admission to a healthcare service
.... dischargeDisposition S0..1CodeableConceptSeparation Mode
... location S0..*BackboneElementList of locations where the patient has been
.... location S1..1Reference(AU Core Location)Location the encounter takes place
... serviceProvider S0..1Reference(AU Core Organization)The organization (facility) responsible for this encounter

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
Encounter.typepreferredhttps://healthterminologies.gov.au/fhir/ValueSet/encounter-type-1
Encounter.serviceTypepreferredhttps://healthterminologies.gov.au/fhir/ValueSet/service-type-1
NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..*AUBaseEncounterAn encounter in an Australian healthcare context
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... encounterDescription S0..1stringDescription, overview or summary of an encounter
URL: http://hl7.org.au/fhir/StructureDefinition/encounter-description
... associatedHealthcareService 0..*Reference(HealthcareService)Associated healthcare service
URL: http://hl7.org.au/fhir/StructureDefinition/associated-healthcareservice
... identifier SΣ0..*IdentifierIdentifier(s) by which this encounter is known
... status ?!SΣ1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
Binding: EncounterStatus (required): Current state of the encounter.

... class SΣ1..1CodingClassification of patient encounter
Binding: ActEncounterCode - AU Extended (extensible)
... type SΣ0..*CodeableConceptSpecific type of encounter
Binding: https://healthterminologies.gov.au/fhir/ValueSet/encounter-type-1 (preferred)
... serviceType SΣ0..1CodeableConceptSpecific type of service
Binding: https://healthterminologies.gov.au/fhir/ValueSet/service-type-1 (preferred)
... subject SΣ1..1Reference(AU Core Patient)The patient or group present at the encounter
... participant SΣ0..*BackboneElementList of participants involved in the encounter
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... type SΣ0..*CodeableConceptRole of participant in encounter
Binding: ParticipantType (extensible): Role of participant in encounter.


.... individual SΣ0..1Reference(AU Core Practitioner | AU Core PractitionerRole | AU Core RelatedPerson)Persons involved in the encounter other than the patient
... period S1..1PeriodThe start and end time of the encounter
... reasonCode SΣ0..*CodeableConceptCoded reason the encounter takes place
Binding: EncounterReasonCodes (preferred): Reason why the encounter takes place.


... reasonReference SΣ0..*Reference(AU Core Condition | AU Core Observation | AU Core Procedure)Reason the encounter takes place (reference)
... hospitalization S0..1BackboneElementDetails about the admission to a healthcare service
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... dischargeDisposition S0..1CodeableConceptSeparation Mode
Binding: https://healthterminologies.gov.au/fhir/ValueSet/separation-mode-1 (extensible)
... location S0..*BackboneElementList of locations where the patient has been
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... location S1..1Reference(AU Core Location)Location the encounter takes place
... serviceProvider S0..1Reference(AU Core Organization)The organization (facility) responsible for this encounter

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Encounter.statusrequiredEncounterStatus
Encounter.classextensibleActEncounterCodeAUExtended
Encounter.typepreferredhttps://healthterminologies.gov.au/fhir/ValueSet/encounter-type-1
Encounter.serviceTypepreferredhttps://healthterminologies.gov.au/fhir/ValueSet/service-type-1
Encounter.participant.typeextensibleParticipantType
Encounter.reasonCodepreferredEncounterReasonCodes
Encounter.hospitalization.dischargeDispositionextensiblehttps://healthterminologies.gov.au/fhir/ValueSet/separation-mode-1
NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..*AUBaseEncounterAn encounter in an Australian healthcare context
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... encounterDescription S0..1stringDescription, overview or summary of an encounter
URL: http://hl7.org.au/fhir/StructureDefinition/encounter-description
... associatedHealthcareService 0..*Reference(HealthcareService)Associated healthcare service
URL: http://hl7.org.au/fhir/StructureDefinition/associated-healthcareservice
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier SΣ0..*IdentifierIdentifier(s) by which this encounter is known
... status ?!SΣ1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
Binding: EncounterStatus (required): Current state of the encounter.

... statusHistory 0..*BackboneElementList of past encounter statuses
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... status 1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
Binding: EncounterStatus (required): Current state of the encounter.

.... period 1..1PeriodThe time that the episode was in the specified status
... class SΣ1..1CodingClassification of patient encounter
Binding: ActEncounterCode - AU Extended (extensible)
... classHistory 0..*BackboneElementList of past encounter classes
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... class 1..1Codinginpatient | outpatient | ambulatory | emergency +
Binding: ActEncounterCode (extensible): Classification of the encounter.

.... period 1..1PeriodThe time that the episode was in the specified class
... type SΣ0..*CodeableConceptSpecific type of encounter
Binding: https://healthterminologies.gov.au/fhir/ValueSet/encounter-type-1 (preferred)
... serviceType SΣ0..1CodeableConceptSpecific type of service
Binding: https://healthterminologies.gov.au/fhir/ValueSet/service-type-1 (preferred)
... priority 0..1CodeableConceptIndicates the urgency of the encounter
Binding: ActPriority (example): Indicates the urgency of the encounter.

... subject SΣ1..1Reference(AU Core Patient)The patient or group present at the encounter
... episodeOfCare Σ0..*Reference(EpisodeOfCare)Episode(s) of care that this encounter should be recorded against
... basedOn 0..*Reference(ServiceRequest)The ServiceRequest that initiated this encounter
... participant SΣ0..*BackboneElementList of participants involved in the encounter
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... type SΣ0..*CodeableConceptRole of participant in encounter
Binding: ParticipantType (extensible): Role of participant in encounter.


.... period 0..1PeriodPeriod of time during the encounter that the participant participated
.... individual SΣ0..1Reference(AU Core Practitioner | AU Core PractitionerRole | AU Core RelatedPerson)Persons involved in the encounter other than the patient
... appointment Σ0..*Reference(Appointment)The appointment that scheduled this encounter
... period S1..1PeriodThe start and end time of the encounter
... length 0..1DurationQuantity of time the encounter lasted (less time absent)
... reasonCode SΣ0..*CodeableConceptCoded reason the encounter takes place
Binding: EncounterReasonCodes (preferred): Reason why the encounter takes place.


... reasonReference SΣ0..*Reference(AU Core Condition | AU Core Observation | AU Core Procedure)Reason the encounter takes place (reference)
... diagnosis Σ0..*BackboneElementThe list of diagnosis relevant to this encounter
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... condition Σ1..1Reference(Condition | Procedure)The diagnosis or procedure relevant to the encounter
.... use 0..1CodeableConceptRole that this diagnosis has within the encounter (e.g. admission, billing, discharge …)
Binding: DiagnosisRole (preferred): The type of diagnosis this condition represents.

.... rank 0..1positiveIntRanking of the diagnosis (for each role type)
... account 0..*Reference(Account)The set of accounts that may be used for billing for this Encounter
... hospitalization S0..1BackboneElementDetails about the admission to a healthcare service
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... preAdmissionIdentifier 0..1IdentifierPre-admission identifier
.... origin 0..1Reference(Location | Organization)The location/organization from which the patient came before admission
.... admitSource 0..1CodeableConceptFrom where patient was admitted (physician referral, transfer)
Binding: AdmitSource (preferred): From where the patient was admitted.

.... reAdmission 0..1CodeableConceptThe type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission
Binding: hl7VS-re-admissionIndicator (example): The reason for re-admission of this hospitalization encounter.

.... dietPreference 0..*CodeableConceptDiet preferences reported by the patient
Binding: Diet (example): Medical, cultural or ethical food preferences to help with catering requirements.


.... specialCourtesy 0..*CodeableConceptSpecial courtesies (VIP, board member)
Binding: SpecialCourtesy (preferred): Special courtesies.


.... specialArrangement 0..*CodeableConceptWheelchair, translator, stretcher, etc.
Binding: SpecialArrangements (preferred): Special arrangements.


.... destination 0..1Reference(Location | Organization)Location/organization to which the patient is discharged
.... dischargeDisposition S0..1CodeableConceptSeparation Mode
Binding: https://healthterminologies.gov.au/fhir/ValueSet/separation-mode-1 (extensible)
... location S0..*BackboneElementList of locations where the patient has been
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... location S1..1Reference(AU Core Location)Location the encounter takes place
.... status 0..1codeplanned | active | reserved | completed
Binding: EncounterLocationStatus (required): The status of the location.

.... physicalType 0..1CodeableConceptThe physical type of the location (usually the level in the location hierachy - bed room ward etc.)
Binding: LocationType (example): Physical form of the location.

.... period 0..1PeriodTime period during which the patient was present at the location
... serviceProvider S0..1Reference(AU Core Organization)The organization (facility) responsible for this encounter
... partOf 0..1Reference(Encounter)Another Encounter this encounter is part of

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Encounter.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
Encounter.statusrequiredEncounterStatus
Encounter.statusHistory.statusrequiredEncounterStatus
Encounter.classextensibleActEncounterCodeAUExtended
Encounter.classHistory.classextensibleActEncounterCode
Encounter.typepreferredhttps://healthterminologies.gov.au/fhir/ValueSet/encounter-type-1
Encounter.serviceTypepreferredhttps://healthterminologies.gov.au/fhir/ValueSet/service-type-1
Encounter.priorityexampleActPriority
Encounter.participant.typeextensibleParticipantType
Encounter.reasonCodepreferredEncounterReasonCodes
Encounter.diagnosis.usepreferredDiagnosisRole
Encounter.hospitalization.admitSourcepreferredAdmitSource
Encounter.hospitalization.reAdmissionexampleHl7VSReAdmissionIndicator
Encounter.hospitalization.dietPreferenceexampleDiet
Encounter.hospitalization.specialCourtesypreferredSpecialCourtesy
Encounter.hospitalization.specialArrangementpreferredSpecialArrangements
Encounter.hospitalization.dischargeDispositionextensiblehttps://healthterminologies.gov.au/fhir/ValueSet/separation-mode-1
Encounter.location.statusrequiredEncounterLocationStatus
Encounter.location.physicalTypeexampleLocationType

Differential View

This structure is derived from AUBaseEncounter

NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..*AUBaseEncounterAn encounter in an Australian healthcare context
... extension:encounterDescription S0..1EncounterDescriptionDescription, overview or summary of an encounter
... identifier S0..*IdentifierIdentifier(s) by which this encounter is known
... status S1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
... type S0..*CodeableConceptSpecific type of encounter
Binding: https://healthterminologies.gov.au/fhir/ValueSet/encounter-type-1 (preferred)
... serviceType S0..1CodeableConceptSpecific type of service
Binding: https://healthterminologies.gov.au/fhir/ValueSet/service-type-1 (preferred)
... subject S1..1Reference(AU Core Patient)The patient or group present at the encounter
... participant S0..*BackboneElementList of participants involved in the encounter
.... type S0..*CodeableConceptRole of participant in encounter
.... individual S0..1Reference(AU Core Practitioner | AU Core PractitionerRole | AU Core RelatedPerson)Persons involved in the encounter other than the patient
... period S1..1PeriodThe start and end time of the encounter
... reasonCode S0..*CodeableConceptCoded reason the encounter takes place
... reasonReference[x] S0..*Reference(AU Core Condition | AU Core Observation | AU Core Procedure)Reason the encounter takes place (reference)
... hospitalization S0..1BackboneElementDetails about the admission to a healthcare service
.... dischargeDisposition S0..1CodeableConceptSeparation Mode
... location S0..*BackboneElementList of locations where the patient has been
.... location S1..1Reference(AU Core Location)Location the encounter takes place
... serviceProvider S0..1Reference(AU Core Organization)The organization (facility) responsible for this encounter

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet
Encounter.typepreferredhttps://healthterminologies.gov.au/fhir/ValueSet/encounter-type-1
Encounter.serviceTypepreferredhttps://healthterminologies.gov.au/fhir/ValueSet/service-type-1

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..*AUBaseEncounterAn encounter in an Australian healthcare context
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... encounterDescription S0..1stringDescription, overview or summary of an encounter
URL: http://hl7.org.au/fhir/StructureDefinition/encounter-description
... associatedHealthcareService 0..*Reference(HealthcareService)Associated healthcare service
URL: http://hl7.org.au/fhir/StructureDefinition/associated-healthcareservice
... identifier SΣ0..*IdentifierIdentifier(s) by which this encounter is known
... status ?!SΣ1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
Binding: EncounterStatus (required): Current state of the encounter.

... class SΣ1..1CodingClassification of patient encounter
Binding: ActEncounterCode - AU Extended (extensible)
... type SΣ0..*CodeableConceptSpecific type of encounter
Binding: https://healthterminologies.gov.au/fhir/ValueSet/encounter-type-1 (preferred)
... serviceType SΣ0..1CodeableConceptSpecific type of service
Binding: https://healthterminologies.gov.au/fhir/ValueSet/service-type-1 (preferred)
... subject SΣ1..1Reference(AU Core Patient)The patient or group present at the encounter
... participant SΣ0..*BackboneElementList of participants involved in the encounter
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... type SΣ0..*CodeableConceptRole of participant in encounter
Binding: ParticipantType (extensible): Role of participant in encounter.


.... individual SΣ0..1Reference(AU Core Practitioner | AU Core PractitionerRole | AU Core RelatedPerson)Persons involved in the encounter other than the patient
... period S1..1PeriodThe start and end time of the encounter
... reasonCode SΣ0..*CodeableConceptCoded reason the encounter takes place
Binding: EncounterReasonCodes (preferred): Reason why the encounter takes place.


... reasonReference SΣ0..*Reference(AU Core Condition | AU Core Observation | AU Core Procedure)Reason the encounter takes place (reference)
... hospitalization S0..1BackboneElementDetails about the admission to a healthcare service
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... dischargeDisposition S0..1CodeableConceptSeparation Mode
Binding: https://healthterminologies.gov.au/fhir/ValueSet/separation-mode-1 (extensible)
... location S0..*BackboneElementList of locations where the patient has been
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... location S1..1Reference(AU Core Location)Location the encounter takes place
... serviceProvider S0..1Reference(AU Core Organization)The organization (facility) responsible for this encounter

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Encounter.statusrequiredEncounterStatus
Encounter.classextensibleActEncounterCodeAUExtended
Encounter.typepreferredhttps://healthterminologies.gov.au/fhir/ValueSet/encounter-type-1
Encounter.serviceTypepreferredhttps://healthterminologies.gov.au/fhir/ValueSet/service-type-1
Encounter.participant.typeextensibleParticipantType
Encounter.reasonCodepreferredEncounterReasonCodes
Encounter.hospitalization.dischargeDispositionextensiblehttps://healthterminologies.gov.au/fhir/ValueSet/separation-mode-1

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Encounter 0..*AUBaseEncounterAn encounter in an Australian healthcare context
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... encounterDescription S0..1stringDescription, overview or summary of an encounter
URL: http://hl7.org.au/fhir/StructureDefinition/encounter-description
... associatedHealthcareService 0..*Reference(HealthcareService)Associated healthcare service
URL: http://hl7.org.au/fhir/StructureDefinition/associated-healthcareservice
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier SΣ0..*IdentifierIdentifier(s) by which this encounter is known
... status ?!SΣ1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
Binding: EncounterStatus (required): Current state of the encounter.

... statusHistory 0..*BackboneElementList of past encounter statuses
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... status 1..1codeplanned | arrived | triaged | in-progress | onleave | finished | cancelled +
Binding: EncounterStatus (required): Current state of the encounter.

.... period 1..1PeriodThe time that the episode was in the specified status
... class SΣ1..1CodingClassification of patient encounter
Binding: ActEncounterCode - AU Extended (extensible)
... classHistory 0..*BackboneElementList of past encounter classes
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... class 1..1Codinginpatient | outpatient | ambulatory | emergency +
Binding: ActEncounterCode (extensible): Classification of the encounter.

.... period 1..1PeriodThe time that the episode was in the specified class
... type SΣ0..*CodeableConceptSpecific type of encounter
Binding: https://healthterminologies.gov.au/fhir/ValueSet/encounter-type-1 (preferred)
... serviceType SΣ0..1CodeableConceptSpecific type of service
Binding: https://healthterminologies.gov.au/fhir/ValueSet/service-type-1 (preferred)
... priority 0..1CodeableConceptIndicates the urgency of the encounter
Binding: ActPriority (example): Indicates the urgency of the encounter.

... subject SΣ1..1Reference(AU Core Patient)The patient or group present at the encounter
... episodeOfCare Σ0..*Reference(EpisodeOfCare)Episode(s) of care that this encounter should be recorded against
... basedOn 0..*Reference(ServiceRequest)The ServiceRequest that initiated this encounter
... participant SΣ0..*BackboneElementList of participants involved in the encounter
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... type SΣ0..*CodeableConceptRole of participant in encounter
Binding: ParticipantType (extensible): Role of participant in encounter.


.... period 0..1PeriodPeriod of time during the encounter that the participant participated
.... individual SΣ0..1Reference(AU Core Practitioner | AU Core PractitionerRole | AU Core RelatedPerson)Persons involved in the encounter other than the patient
... appointment Σ0..*Reference(Appointment)The appointment that scheduled this encounter
... period S1..1PeriodThe start and end time of the encounter
... length 0..1DurationQuantity of time the encounter lasted (less time absent)
... reasonCode SΣ0..*CodeableConceptCoded reason the encounter takes place
Binding: EncounterReasonCodes (preferred): Reason why the encounter takes place.


... reasonReference SΣ0..*Reference(AU Core Condition | AU Core Observation | AU Core Procedure)Reason the encounter takes place (reference)
... diagnosis Σ0..*BackboneElementThe list of diagnosis relevant to this encounter
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... condition Σ1..1Reference(Condition | Procedure)The diagnosis or procedure relevant to the encounter
.... use 0..1CodeableConceptRole that this diagnosis has within the encounter (e.g. admission, billing, discharge …)
Binding: DiagnosisRole (preferred): The type of diagnosis this condition represents.

.... rank 0..1positiveIntRanking of the diagnosis (for each role type)
... account 0..*Reference(Account)The set of accounts that may be used for billing for this Encounter
... hospitalization S0..1BackboneElementDetails about the admission to a healthcare service
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... preAdmissionIdentifier 0..1IdentifierPre-admission identifier
.... origin 0..1Reference(Location | Organization)The location/organization from which the patient came before admission
.... admitSource 0..1CodeableConceptFrom where patient was admitted (physician referral, transfer)
Binding: AdmitSource (preferred): From where the patient was admitted.

.... reAdmission 0..1CodeableConceptThe type of hospital re-admission that has occurred (if any). If the value is absent, then this is not identified as a readmission
Binding: hl7VS-re-admissionIndicator (example): The reason for re-admission of this hospitalization encounter.

.... dietPreference 0..*CodeableConceptDiet preferences reported by the patient
Binding: Diet (example): Medical, cultural or ethical food preferences to help with catering requirements.


.... specialCourtesy 0..*CodeableConceptSpecial courtesies (VIP, board member)
Binding: SpecialCourtesy (preferred): Special courtesies.


.... specialArrangement 0..*CodeableConceptWheelchair, translator, stretcher, etc.
Binding: SpecialArrangements (preferred): Special arrangements.


.... destination 0..1Reference(Location | Organization)Location/organization to which the patient is discharged
.... dischargeDisposition S0..1CodeableConceptSeparation Mode
Binding: https://healthterminologies.gov.au/fhir/ValueSet/separation-mode-1 (extensible)
... location S0..*BackboneElementList of locations where the patient has been
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... location S1..1Reference(AU Core Location)Location the encounter takes place
.... status 0..1codeplanned | active | reserved | completed
Binding: EncounterLocationStatus (required): The status of the location.

.... physicalType 0..1CodeableConceptThe physical type of the location (usually the level in the location hierachy - bed room ward etc.)
Binding: LocationType (example): Physical form of the location.

.... period 0..1PeriodTime period during which the patient was present at the location
... serviceProvider S0..1Reference(AU Core Organization)The organization (facility) responsible for this encounter
... partOf 0..1Reference(Encounter)Another Encounter this encounter is part of

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Encounter.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
Encounter.statusrequiredEncounterStatus
Encounter.statusHistory.statusrequiredEncounterStatus
Encounter.classextensibleActEncounterCodeAUExtended
Encounter.classHistory.classextensibleActEncounterCode
Encounter.typepreferredhttps://healthterminologies.gov.au/fhir/ValueSet/encounter-type-1
Encounter.serviceTypepreferredhttps://healthterminologies.gov.au/fhir/ValueSet/service-type-1
Encounter.priorityexampleActPriority
Encounter.participant.typeextensibleParticipantType
Encounter.reasonCodepreferredEncounterReasonCodes
Encounter.diagnosis.usepreferredDiagnosisRole
Encounter.hospitalization.admitSourcepreferredAdmitSource
Encounter.hospitalization.reAdmissionexampleHl7VSReAdmissionIndicator
Encounter.hospitalization.dietPreferenceexampleDiet
Encounter.hospitalization.specialCourtesypreferredSpecialCourtesy
Encounter.hospitalization.specialArrangementpreferredSpecialArrangements
Encounter.hospitalization.dischargeDispositionextensiblehttps://healthterminologies.gov.au/fhir/ValueSet/separation-mode-1
Encounter.location.statusrequiredEncounterLocationStatus
Encounter.location.physicalTypeexampleLocationType

 

Other representations of profile: CSV, Excel, Schematron

Notes:

Below is an overview of the mandatory and optional search parameters and combined search parameters. FHIR search operations and the syntax used to describe the interactions is described 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 client SHALL provide at least an id value and MAY provide both the Type and id values. The server SHALL support both.
patient+date SHALL reference+date
patient+class SHOULD reference+token
patient+discharge-disposition SHOULD reference+token
patient.identifier SHOULD reference.token The client SHALL provide both the system and code values. The server SHALL support both.

The client SHOULD support search using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. The server SHOULD support search using the using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile.
patient+location SHOULD reference+reference
patient+status SHOULD reference+token
patient+type SHOULD reference+token
class MAY token The client SHALL provide at least a code value and MAY provide both the system and code values. The server SHALL support both.
date MAY date A client SHALL provide a value precise to the second + time offset. A server SHALL support a value precise to the second + time offset.
discharge-disposition MAY token The client SHALL provide at least a code value and MAY provide both the system and code values. The server SHALL support both.
identifier MAY token The client SHALL provide at least a code value and MAY provide both the system and code values. The server SHALL support both.
location MAY reference The client SHALL provide at least an id value and MAY provide both the Type and id values. The server SHALL support both.
status MAY token The client SHALL provide at least a code value and MAY provide both the system and code values. The server SHALL support both.
type MAY token The client SHALL provide at least a code value and MAY provide both the system and code values. The server SHALL support both.

Mandatory Search Parameters:

The following search parameters and search parameter combinations SHALL be supported:

  1. SHALL support searching using the patient search parameter:
    • SHALL support these _revinclude parameters: Provenance:target
    • SHOULD support chained searching of patient canonical identifier patient.identifier (e.g. patient.identifier=[system|][code])

    GET [base]/Encounter?patient={Type/}[id] or optionally GET [base]/Encounter?patient.identifier=[system|][code]

    Example:

    1. GET [base]/Encounter?patient=5678
    2. GET [base]/Encounter?patient.identifier=http://ns.electronichealth.net.au/id/medicare-number|32788511952
    3. GET [base]/Encounter?patient.identifier=http://ns.electronichealth.net.au/id/hi/ihi/1.0|8003608833357361

    Implementation Notes: Fetches a bundle of all Encounter resources for the specified patient (how to search by reference and how to search by token)

  2. SHALL support searching using the combination of the patient and date search parameters:
    • SHALL support these _revinclude parameters: Provenance:target
    • SHOULD support chained searching of patient canonical identifier patient.identifier (e.g. patient.identifier=[system|][code])
    • SHALL support these date comparators: gt,lt,ge,le
    • SHOULD support multipleAnd search on date (e.g.date=[date]&date=[date]]&...)

    GET [base]/Encounter?patient={Type/}[id]&date={gt|lt|ge|le}[date]{&date={gt|lt|ge|le}[date]&...}

    Example:

    1. GET [base]/Encounter?patient=5678&date=ge2020-01-01T00:00:00Z

    Implementation Notes: Fetches a bundle of all Encounter resources for the specified patient and date (how to search by reference and how to search by date)

Optional Search Parameters:

The following search parameters and search parameter combinations SHOULD be supported:

  1. SHOULD support searching using the combination of the patient and class search parameters:
    • SHALL support these _revinclude parameters: Provenance:target
    • SHOULD support chained searching of patient canonical identifier patient.identifier (e.g. patient.identifier=[system|][code])

    GET [base]/Encounter?patient={Type/}[id]&class={system|}[code]

    Example:

    1. GET [base]/Encounter?patient=5678&class=http://terminology.hl7.org/CodeSystem/v3-ActCode|AMB

    Implementation Notes: Fetches a bundle of all Encounter resources for the specified patient and class (how to search by reference and how to search by token)

  2. SHOULD support searching using the combination of the patient and discharge-disposition search parameters:
    • SHALL support these _revinclude parameters: Provenance:target
    • SHOULD support chained searching of patient canonical identifier patient.identifier (e.g. patient.identifier=[system|][code])

    GET [base]/Encounter?patient={Type/}[id]&discharge-disposition={system|}[code]

    Example:

    1. GET [base]/Encounter?patient=5678&discharge-disposition=9
    2. GET [base]/Encounter?patient=5678&discharge-disposition=9&_revinclude=Provenance:target

    Implementation Notes: Fetches a bundle of all Encounter resources for the specified patient and discharge disposition (how to search by reference and how to search by token)

  3. SHOULD support searching using the combination of the patient and location search parameters:
    • SHALL support these _revinclude parameters: Provenance:target
    • SHOULD support chained searching of patient canonical identifier patient.identifier (e.g. patient.identifier=[system|][code])

    GET [base]/Encounter?patient={Type/}[id]&location={Type/}[id]

    Example:

    1. GET [base]/Encounter?patient=5678&location=Location/vic-hospital

    Implementation Notes: Fetches a bundle of all Encounter resources matching the specified patient and location (how to search by reference