AU Base Implementation Guide
6.0.1-ci-build - CI Build

AU Base Implementation Guide, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 6.0.1-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-base/ and changes regularly. See the Directory of published versions

## ValueSet: Contact Purpose

Official URL: http://terminology.hl7.org.au/ValueSet/contact-purpose | Version: 6.0.1-ci-build
Standards status: Trial-use | Maturity Level: 1 | Computable Name: ContactPurpose
Other Identifiers: OID:2.16.840.1.113883.2.3.4.2.4.19
Copyright/Legal: HL7 Australia© 2018+; Licensed Under Creative Commons No Rights Reserved.

The purpose for which an associated contact can be reached.

References

- AU Base Organization
- Contact Purpose

Changes since version 5.0.0:

- No changes

### Logical Definition (CLD)

Profile: `https://healthterminologies.gov.au/fhir/StructureDefinition/composed-value-set-4`

This value set includes codes based on the following rules:

- Include all codes defined in `http://terminology.hl7.org.au/CodeSystem/contact-purpose` version 📦6.0.1-ci-build
- Import all the codes that are contained in Contact entity type

### Expansion

Expansion performed internally based on:

- codesystem Contact Purpose v6.0.1-ci-build (CodeSystem)
- codesystem Contact entity type v2.0.0 (CodeSystem)
- valueset Contact entity type v2.0.0 (ValueSet)

This value set contains 12 concepts

System | Code | Display (en) | Definition | JSON | XML
`http://terminology.hl7.org.au/CodeSystem/contact-purpose` | after-hours | After Hours | Contact to be used during an after hours period as determined by the contact entity. An after hours period is a period of time outside of normal operating periods of the entity or service. |  |
`http://terminology.hl7.org.au/CodeSystem/contact-purpose` | medical-record | Medical Record | Contact for medical/clinical records including provision of results to a practitioner or the correction of a clinical record. |  |
`http://terminology.hl7.org.au/CodeSystem/contact-purpose` | emergency | Emergency | Contact to be used in an emergency. |  |
`http://terminology.hl7.org.au/CodeSystem/contact-purpose` | clinical-emergency | Clinical Emergency | Contact to be used in a clinical emergency. |  |
`http://terminology.hl7.org.au/CodeSystem/contact-purpose` | legal | Legal | Contact for legal concerns or enquiries. |  |
`http://terminology.hl7.org.au/CodeSystem/contact-purpose` | privacy | Privacy | Contact for concerns or enquiries relating to privacy of information. |  |
`http://terminology.hl7.org/CodeSystem/contactentity-type` | BILL | Billing | Contact details for information regarding to billing/general finance enquiries. |  |
`http://terminology.hl7.org/CodeSystem/contactentity-type` | ADMIN | Administrative | Contact details for administrative enquiries. |  |
`http://terminology.hl7.org/CodeSystem/contactentity-type` | HR | Human Resource | Contact details for issues related to Human Resources, such as staff matters, OH&S etc. |  |
`http://terminology.hl7.org/CodeSystem/contactentity-type` | PAYOR | Payor | Contact details for dealing with issues related to insurance claims/adjudication/payment. |  |
`http://terminology.hl7.org/CodeSystem/contactentity-type` | PATINF | Patient | Generic information contact for patients. |  |
`http://terminology.hl7.org/CodeSystem/contactentity-type` | PRESS | Press | Dedicated contact point for matters relating to press enquiries. |  |

Explanation of the columns that may appear on this page:

Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System | The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code | The code (used as the code in the resource instance)
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition | An explanation of the meaning of the concept
Comments | Additional notes about how to use the code