Provider Connect Australia (PCA) - Local Development build (v24.2.0.1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Official URL: http://pca.digitalhealth.gov.au/fhir/4.0/ValueSet/pca-key-contact-type | Version: 24.2.0.1 | |||
Active as of 2024-11-25 | Computable Name: PcaKeyContactType | |||
Copyright/Legal: Copyright © 2024 Australian Digital Health Agency - All rights reserved. This content is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/. |
The PCA Key Contact Type valueset includes concepts that identify the types of PCA Key Contacts that can be recorded against a PCA Healthcare Service.
References
Generated Narrative: ValueSet pca-key-contact-type
http://pca.digitalhealth.gov.au/fhir/4.0/CodeSystem/pca-key-contact-type
Generated Narrative: ValueSet
Expansion based on codesystem PCA Key Contact Type v24.2.0.1 (CodeSystem)
This value set contains 4 concepts
Code | System | Display | Definition |
billing-agent | http://pca.digitalhealth.gov.au/fhir/4.0/CodeSystem/pca-key-contact-type | Billing agent | Billing agent |
ict-contact | http://pca.digitalhealth.gov.au/fhir/4.0/CodeSystem/pca-key-contact-type | ICT contact | ICT contact |
practice-manager | http://pca.digitalhealth.gov.au/fhir/4.0/CodeSystem/pca-key-contact-type | Practice manager | Practice manager |
finance-manager | http://pca.digitalhealth.gov.au/fhir/4.0/CodeSystem/pca-key-contact-type | Finance manager | Finance manager |
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 |