AU Core Implementation Guide
1.1.0-ci-build - CI Build
AU Core Implementation Guide, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 1.1.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/AuDigitalHealth/au-fhir-core/ and changes regularly. See the Directory of published versions
Official URL: http://hl7.org.au/fhir/core/StructureDefinition/au-core-condition | Version: 1.1.0-ci-build | |||
Standards status: Trial-use | Maturity Level: 2 | Computable Name: AUCoreCondition | ||
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 a Condition resource to record, search, and fetch problems, diagnoses, and health concerns associated with a patient. It is based on the AU Base Condition profile and identifies the additional mandatory core elements, extensions, vocabularies and value sets that SHALL be present in the Condition resource when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.
See Comparison with other national and international IGs for a comparison between AU Core profiles and profiles in other implementation guides.
The following are supported usage scenarios for this profile:
Condition.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.Condition.code.text
and/or Condition.code.coding.display
so that requesters can display the condition even if the requester does not recognise the code supplied.Condition.clinicalStatus
Condition.code
:
Condition.code
SHOULD use the code SNOMED CT 160245001 |No current problems or disability (situation)|Condition.code
and Condition.verificationStatus
of “confirmed” or “unconfirmed”Usage:
Changes since version 1.0.0:
Description of Profiles, Differentials, Snapshots and how the different presentations work.
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. The requester SHOULD support chained search patient.identifier using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. The responder SHOULD support chained search patient.identifier using IHI, Medicare Number, and DVA Number identifiers as defined in the AU Core Patient profile. |
patient+category | SHALL | reference +token |
|
patient+clinical-status | SHALL | reference +token |
|
patient+category+clinical-status | SHOULD | reference +token +token |
|
patient+code | SHOULD | reference +token |
|
patient+onset-date | SHOULD | reference +date |
|
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. |
clinical-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. |
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 SHOULD support multipleOr . The responder SHOULD support multipleOr . |
onset-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. The requester SHALL support these search comparators gt , lt , ge , le . The responder SHALL support these search comparators gt , lt , ge , le .The requester SHOULD support multipleAnd , and if multipleAnd is supported, SHALL support the search comparators gt , lt , ge , le . The responder SHOULD support multipleAnd , and if multipleAnd is supported, SHALL support the search comparators gt , lt , ge , le . |
The following search parameters and search parameter combinations SHALL be supported:
patient
search parameter:
patient.identifier
(e.g. patient.identifier=[system|][code]
)GET [base]/Condition?patient={Type/}[id]
or optionally GET [base]/Condition?patient.identifier=[system|][code]
Example:
Implementation Notes: Fetches a bundle of all Condition 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]/Condition?patient={Type/}[id]&category={system|}[code]
Example:
Implementation Notes: Fetches a bundle of all Condition resources for the specified patient and category code = encounter-diagnosis
(how to search by reference and how to search by token)
patient
and clinical-status
search parameters:
patient.identifier
(e.g. patient.identifier=[system|][code]
)GET [base]/Condition?patient={Type/}[id]&clinical-status={system|}[code]
Example:
Implementation Notes: Fetches a bundle of all Condition resources for the specified patient and a clinical status (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 clinical-status
search parameters:
patient.identifier
(e.g. patient.identifier=[system|][code]
)GET [base]/Condition?patient={Type/}[id]&category={system|}[code]&clinical-status={system|}[code]
Example:
Implementation Notes: Fetches a bundle of all Condition resources for the specified patient and category and clinical-status (how to search by reference and how to search by token)
patient
and code
search parameters:
patient.identifier
(e.g. patient.identifier=[system|][code]
)code
(e.g.code={system|}[code],{system|}[code],...
)GET [base]/Condition?patient={Type/}[id]&code={system|}[code]{,{system|}[code],...}
Example:
Implementation Notes: Fetches a bundle of all Condition resources for the specified patient and condition code(s). SHOULD support search by multiple codes. The Condition code
parameter searches Condition.code
only. (how to search by reference and how to search by token)
patient
and onset-date
search parameters:
patient.identifier
(e.g. patient.identifier=[system|][code]
)onset-date
comparators: gt,lt,ge,le
onset-date
(e.g.onset-date=[date]&date=[date]]&...
), and if multipleAnd is supported, SHALL support the search comparators gt,lt,ge,le
GET [base]/Condition?patient={Type/}[id]&onset-date={gt|lt|ge|le}[date]{&date={gt|lt|ge|le}[date]&...}
Example:
Implementation Notes: Fetches a bundle of all Condition resources for the specified patient and onset-date (how to search by reference and how to search by date)