Health New Zealand Te Whatu Ora Shared Care FHIR API
0.4.4 - release

Health New Zealand Te Whatu Ora Shared Care FHIR API - Local Development build (v0.4.4) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

## ValueSet: NZ purpose of use

Official URL: https://nzhts.digital.health.nz/fhir/ValueSet/nz-purpose-of-use-value-set | Version: 20240725
Draft as of 2023-08-01 | Computable Name: NZPurposeOfUse
Other Identifiers: Purposeofinformationuse

Reason for performing one or more operations on information, which may be permitted by source system's security policy in accordance with one or more privacy policies and consent directives. Usage Notes: The rationale or purpose for an act relating to the management of personal health information, such as collecting personal health information for research or public health purposes.

References

- CommunicationPerson

### Logical Definition (CLD)

version: 1; Last updated: 2024-07-25 17:30:07+1200

This value set includes codes based on the following rules:

- Include codes from`http://terminology.hl7.org/CodeSystem/v3-ActReason` where concept is-a PurposeOfUse
- Include all codes defined in `https://standards.digital.health.nz/ns/nz-purpose-of-use`

### Expansion

Expansion performed internally based on:

- codesystem ActReason v3.1.0 (CodeSystem)
- codesystem NZ Purpose Of Use v20240725 (CodeSystem)

This value set contains 68 concepts

Code | System | Display | Definition
PurposeOfUse | http://terminology.hl7.org/CodeSystem/v3-ActReason | purpose of use | Reason for performing one or more operations on information, which may be permitted by source system's security policy in accordance with one or more privacy policies and consent directives. Usage Notes: The rationale or purpose for an act relating to the management of personal health information, such as collecting personal health information for research or public health purposes.
HMARKT | http://terminology.hl7.org/CodeSystem/v3-ActReason | healthcare marketing | To perform one or more operations on information for marketing services and products related to health care.
HOPERAT | http://terminology.hl7.org/CodeSystem/v3-ActReason | healthcare operations | To perform one or more operations on information used for conducting administrative and contractual activities related to the provision of health care.
CAREMGT | http://terminology.hl7.org/CodeSystem/v3-ActReason | care management | To perform analytics, evaluation and other secondary uses of treatment and healthcare related information to manage the quality, efficacy, patient safety, population health, and cost effectiveness of healthcare delivery. Explicitly excludes the use of information to organize the delivery of health care for care coordination and case management, or to provide healthcare treatment. Usage Note: The concept of care management is narrower than the list of activities related to more general organizational objectives such as provider profiling, education of healthcare and non-healthcare professionals; insurance underwriting, premium rating, reinsurance; organizational legal, medical review, auditing, compliance and fraud and abuse detection; business planning, development, and restructuring; fund-raising; and customer service. Map: Maps to ISO 14265 Classification Term "Health service management and quality assurance" described as "To inform persons or processes responsible for determining the availability, quality, safety, equity and cost-effectiveness of health care services." There is a semantic gap in concepts. This classification term is described as activities, i.e., "to inform persons" or "to inform processes" rather than the rationale for performing actions/operations on information related to the activity.
DONAT | http://terminology.hl7.org/CodeSystem/v3-ActReason | donation | To perform one or more operations on information used for cadaveric organ, eye or tissue donation.
FRAUD | http://terminology.hl7.org/CodeSystem/v3-ActReason | fraud | To perform one or more operations on information used for fraud detection and prevention processes.
GOV | http://terminology.hl7.org/CodeSystem/v3-ActReason | government | To perform one or more operations on information used within government processes.
HACCRED | http://terminology.hl7.org/CodeSystem/v3-ActReason | health accreditation | To perform one or more operations on information for conducting activities related to meeting accreditation criteria.
HCOMPL | http://terminology.hl7.org/CodeSystem/v3-ActReason | health compliance | To perform one or more operations on information used for conducting activities required to meet a mandate.
HDECD | http://terminology.hl7.org/CodeSystem/v3-ActReason | decedent | To perform one or more operations on information used for handling deceased patient matters.
HDIRECT | http://terminology.hl7.org/CodeSystem/v3-ActReason | directory | To perform one or more operation operations on information used to manage a patient directory. Examples: facility enterprise payer health information exchange patient directory
HDM | http://terminology.hl7.org/CodeSystem/v3-ActReason | healthcare delivery management | To perform one or more actions on information used for conducting administrative and contractual activities by or on behalf of organizational entities responsible for delivery of an individual's benefits in a healthcare program, health plan or insurance. Explicitly excludes the use of information to organize the delivery of health care for care coordination and case management, or to provide healthcare treatment. Usage Note: Examples of activities conducted under this purpose of use: provider profiling, risk adjustment, underwriting, fraud and abuse, quality improvement population health and care management. Aligns with HIPAA Operation POU minus coordination of care or other treatment related activities. Similar to the description in SAMHSA Confidentiality of Substance Use Disorder Patient Records Supplemental notice of proposed rulemaking. Map: Maps to ISO 14265 Classification Term "Administration of care for an individual subject of care" described as "To inform persons or processes responsible for enabling the availability of resources or funding or permissions for providing health care services to the subject of care." However, this classification term is described as activities, i.e., "to inform persons" or "to inform processes" rather than the rationale for performing actions/operations on information related to the activity.
HLEGAL | http://terminology.hl7.org/CodeSystem/v3-ActReason | legal | To perform one or more operations on information for conducting activities required by legal proceeding.
HOUTCOMS | http://terminology.hl7.org/CodeSystem/v3-ActReason | health outcome measure | To perform one or more operations on information used for assessing results and comparative effectiveness achieved by health care practices and interventions.
HPRGRP | http://terminology.hl7.org/CodeSystem/v3-ActReason | health program reporting | To perform one or more operations on information used for conducting activities to meet program accounting requirements.
HQUALIMP | http://terminology.hl7.org/CodeSystem/v3-ActReason | health quality improvement | To perform one or more operations on information used for conducting administrative activities to improve health care quality.
HSYSADMIN | http://terminology.hl7.org/CodeSystem/v3-ActReason | health system administration | To perform one or more operations on information to administer the electronic systems used for the delivery of health care.
LABELING | http://terminology.hl7.org/CodeSystem/v3-ActReason | labeling | To perform one or more operations on information to assign, persist, and manage labels to healthcare data to characterize various aspects, such as its security classification, sensitivity, compartment, integrity, and provenance; applicable privacy, consent, security, provenance, and trust policies; and handling caveats such as purpose of use, obligations, and refrain policies. Label management includes classification of target data by constructing and binding of a label set per applicable policies, security policy information file semantics, and classification guides. Label management also includes process and procedures for subsequent revision of a label for, e.g., reclassification, downgrading classification, and declassification. Label revisions may be triggered by, e.g., expiry of classification period; changes in applicable policy, e.g., revocation of a consent directive; or changes in the governing policy domain in which the data is relocated or a copy of the data is sent. If a label is revised, an audit log should be kept and the provenance of the label changes should be tracked.
METAMGT | http://terminology.hl7.org/CodeSystem/v3-ActReason | metadata management | To perform one or more operations on information to assign, persist, and manage metadata to healthcare data to characterize various aspects used for its indexing, discovery, retrieval, and processing by systems, applications, and end users. For example, master index identifier, media type, and location.
MEMADMIN | http://terminology.hl7.org/CodeSystem/v3-ActReason | member administration | To perform one or more operations on information to administer health care coverage to an enrollee under a policy or program.
MILCDM | http://terminology.hl7.org/CodeSystem/v3-ActReason | military command | To perform one or more operations on information for conducting activities required by military processes, procedures, policies, or law.
PATADMIN | http://terminology.hl7.org/CodeSystem/v3-ActReason | patient administration | To perform one or more operations on information used for operational activities conducted to administer the delivery of health care to a patient.
PATSFTY | http://terminology.hl7.org/CodeSystem/v3-ActReason | patient safety | To perform one or more operations on information in processes related to ensuring the safety of health care.
PERFMSR | http://terminology.hl7.org/CodeSystem/v3-ActReason | performance measure | To perform one or more operations on information used for monitoring performance of recommended health care practices and interventions.
RECORDMGT | http://terminology.hl7.org/CodeSystem/v3-ActReason | records management | To perform one or more operations on information used within the health records management process.
SYSDEV | http://terminology.hl7.org/CodeSystem/v3-ActReason | system development | To perform one or more operations on information to design, develop, implement, test, or deploy a healthcare system or application.
HTEST | http://terminology.hl7.org/CodeSystem/v3-ActReason | test health data | To perform one or more operations on information that is simulated or synthetic health data used for testing system capabilities outside of a production or operational system environment. Usage Note: Data marked with a HTEST security label enables an access control system to permit interfacing systems or end users provisioned with a clearance, which includes a HTEST purpose of use attribute, to test, verify, or validate that a system or application will operate in production as intended based on design specifications.
TRAIN | http://terminology.hl7.org/CodeSystem/v3-ActReason | training | To perform one or more operations on information used in training and education.
MLTRAINING | http://terminology.hl7.org/CodeSystem/v3-ActReason | machine learning training | To perform one or more operations on information used in training a machine learning (AI) model.
HPAYMT | http://terminology.hl7.org/CodeSystem/v3-ActReason | healthcare payment | To perform one or more operations on information for conducting financial or contractual activities related to payment for provision of health care.
CLMATTCH | http://terminology.hl7.org/CodeSystem/v3-ActReason | claim attachment | To perform one or more operations on information for provision of additional clinical evidence in support of a request for coverage or payment for health services.
COVAUTH | http://terminology.hl7.org/CodeSystem/v3-ActReason | coverage authorization | To perform one or more operations on information for conducting prior authorization or predetermination of coverage for services.
COVERAGE | http://terminology.hl7.org/CodeSystem/v3-ActReason | coverage under policy or program | To perform one or more operations on information for conducting activities related to coverage under a program or policy.
ELIGDTRM | http://terminology.hl7.org/CodeSystem/v3-ActReason | eligibility determination | To perform one or more operations on information used for conducting eligibility determination for coverage in a program or policy. May entail review of financial status or disability assessment.
ELIGVER | http://terminology.hl7.org/CodeSystem/v3-ActReason | eligibility verification | To perform one or more operations on information used for conducting eligibility verification of coverage in a program or policy. May entail provider contacting coverage source (e.g., government health program such as workers compensation or health plan) for confirmation of enrollment, eligibility for specific services, and any applicable copays.
ENROLLM | http://terminology.hl7.org/CodeSystem/v3-ActReason | enrollment | To perform one or more operations on information used for enrolling a covered party in a program or policy. May entail recording of covered party's and any dependent's demographic information and benefit choices.
MILDCRG | http://terminology.hl7.org/CodeSystem/v3-ActReason | military discharge | To perform one or more operations on information for the process of releasing military personnel from their service obligations, which may include determining service merit, discharge benefits, and disability assessment.
REMITADV | http://terminology.hl7.org/CodeSystem/v3-ActReason | remittance advice | To perform one or more operations on information about the amount remitted for a health care claim.
PMTDS | http://terminology.hl7.org/CodeSystem/v3-ActReason | decision support assisted payment decision | To apply algorithms (e.g. AI, CDS) to perform one or more operations on information to arrive at decision used in payment for provision of health care.
HRESCH | http://terminology.hl7.org/CodeSystem/v3-ActReason | healthcare research | To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. Use of the data iincludes basic and applied research such as biomedical, population origin or ancestry, translational research, and disease, discipline, specialty specific healthcare research and clinical trial research.
BIORCH | http://terminology.hl7.org/CodeSystem/v3-ActReason | biomedical research | To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. Use of the data must be related to specified biomedical basic or applied research. For example, research on rare plants to determine whether biologic properties may be useful for pharmaceutical development. May be used in combination with clinical trial and other healthcare research purposes of use.
CLINTRCH | http://terminology.hl7.org/CodeSystem/v3-ActReason | clinical trial research | To perform one or more operations on information for conducting scientific investigations in accordance with clinical trial protocols to obtain health care knowledge.
CLINTRCHNPC | http://terminology.hl7.org/CodeSystem/v3-ActReason | clinical trial research without patient care | To perform one or more operations on information for conducting scientific investigations in accordance with clinical trial protocols to obtain health care knowledge without provision of patient care. May be post-coordinated or used with other purposes of use such as disease, discipline, specialty, population origins or ancestry, translational healthcare research. For example, a clinical trial conducted on laboratory specimens collected from a specified patient population.
CLINTRCHPC | http://terminology.hl7.org/CodeSystem/v3-ActReason | clinical trial research with patient care | To perform one or more operations on information for conducting scientific investigations with patient care in accordance with clinical trial protocols to obtain health care knowledge. May be post-coordinated or used with other purposes of use such as disease, discipline, specialty, population origins or ancestry, translational healthcare research. For example, an "off-label" drug used for cancer therapy administer to a specified patient population.
PRECLINTRCH | http://terminology.hl7.org/CodeSystem/v3-ActReason | preclinical trial research | To perform one or more operations on information in preparation for conducting scientific investigation to obtain health care knowledge, such as research on animals or review of patient health records, to determine the feasibility of a clinical trial study; assist with protocol design; or in preparation for institutional review board or ethics committee approval process. May be post-coordinated or used with other purposes of use such as disease, discipline, specialty, population origins or ancestry, translational healthcare research.
DSRCH | http://terminology.hl7.org/CodeSystem/v3-ActReason | disease specific healthcare research | To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge. Use of the data must be related to specified conditions, diagnosis, or disease healthcare research. For example, conducting cancer research by testing reaction of tumor cells to certain biologics. May be used in combination with clinical trial and other healthcare research purposes of use.
POARCH | http://terminology.hl7.org/CodeSystem/v3-ActReason | population origins or ancestry healthcare research | To perform one or more operations on information, including genealogical pedigrees, historical records, surveys, family health data, health records, and genetic information, for conducting scientific investigations to obtain health care knowledge. Use of the data must be related to population origins and/or ancestry healthcare research. For example, gathering genetic specimens from a specific population in order to determine the ancestry and population origins of that group. May be used in combination with clinical trial and other healthcare research purposes of use.
TRANSRCH | http://terminology.hl7.org/CodeSystem/v3-ActReason | translational healthcare research | To perform one or more operations on information for conducting scientific investigations to obtain health care knowledge related to evidence based medicine during the course of providing healthcare treatment. Sometimes referred to as "bench to bedside", which is the iterative feedback loop between healthcare research and clinical trials with input from information collected in the course of routine provision of healthcare. For example, by extending a patient encounter to conduct a survey related to a research topic such as attitudes about use of a wellness device that a patient agreed to use. May be used in combination with clinical trial and other healthcare research purposes of use.
PATRQT | http://terminology.hl7.org/CodeSystem/v3-ActReason | patient requested | To perform one or more operations on information in response to a patient's request.
FAMRQT | http://terminology.hl7.org/CodeSystem/v3-ActReason | family requested | To perform one or more operations on information in response to a request by a family member authorized by the patient.
PWATRNY | http://terminology.hl7.org/CodeSystem/v3-ActReason | power of attorney | To perform one or more operations on information in response to a request by a person appointed as the patient's legal representative.
SUPNWK | http://terminology.hl7.org/CodeSystem/v3-ActReason | support network | To perform one or more operations on information in response to a request by a person authorized by the patient.
PUBHLTH | http://terminology.hl7.org/CodeSystem/v3-ActReason | public health | To perform one or more operations on information for conducting public health activities, such as the reporting of notifiable conditions.
DISASTER | http://terminology.hl7.org/CodeSystem/v3-ActReason | disaster | To perform one or more operations on information used for provision of immediately needed health care to a population of living subjects located in a disaster zone.
THREAT | http://terminology.hl7.org/CodeSystem/v3-ActReason | threat | To perform one or more operations on information used to prevent injury or disease to living subjects who may be the target of violence.
TREAT | http://terminology.hl7.org/CodeSystem/v3-ActReason | treatment | To perform one or more operations on information for provision of health care.
CLINTRL | http://terminology.hl7.org/CodeSystem/v3-ActReason | clinical trial | To perform health care as part of the clinical trial protocol.
COC | http://terminology.hl7.org/CodeSystem/v3-ActReason | coordination of care | To perform one or more actions on information in order to organize the provision and case management of an individual's healthcare, including: Monitoring a person's goals, needs, and preferences; acting as the communication link between two or more participants concerned with a person's health and wellness; organizing and facilitating care activities and promoting self-management by advocating for, empowering, and educating a person; and ensuring safe, appropriate, non-duplicative, and effective integrated care. Usage Note: Use when describing these functions: 1. Monitoring a person's goals, needs, and preferences. 2. Acting as the communication link between two or more participants concerned with a person's health and wellness. 3. Organizing and facilitating care activities and promoting self-management by advocating for, empowering, and educating a person. 4. Ensuring safe, appropriate, non-duplicative, and effective integrated care. The goal is to clearly differentiate this type of coordination of care from HIPAA Operations by specifying that these actions on information are undertaken in the provision of healthcare treatment. For similar uses of this concept, see SAMHSA Confidentiality of Substance Use Disorder Patient Records Supplemental notice of proposed rulemaking, which differentiates concepts of care coordination and case management for the provision of treatment as specifically distinct from activities related to health care delivery management and the operations of organizational entities involved in the delivery of healthcare. Map: Maps to ISO 14265 Classification Terms: "Support of care activities within the provider organisation for an individual subject of care" described as "To inform persons or processes enabling others to provide health care services to the subject of care." "Subject of Care Uses" described as "To inform the subject of care in support of his or her own interests."
ETREAT | http://terminology.hl7.org/CodeSystem/v3-ActReason | Emergency Treatment | To perform one or more operations on information for provision of immediately needed health care for an emergent condition.
BTG | http://terminology.hl7.org/CodeSystem/v3-ActReason | break the glass | To perform policy override operations on information for provision of immediately needed health care for an emergent condition affecting potential harm, death or patient safety by end users who are not provisioned for this purpose of use. Includes override of organizational provisioning policies and may include override of subject of care consent directive restricting access. Map: Partially Maps to ISO 14265 Classification Term "Emergency care provision to an individual subject of care" described as "To inform persons needing to provide health care services to the subject of care urgently, possibly needing to over-ride the policies and consents pertaining to Purpose 1 above." Purpose 1 is equivalent to HL7 treatment purpose of use: "Clinical care provision to an individual subject of care" described as "To inform persons or processes responsible for providing health care services to the subject of care." The ISO description conflates both of the proposed specializations of HL7 ETREAT: break the glass and the typically broader access to health information normally available to providers who are provisioned for emergency workflows on a regular basis, e.g., Emergency Room providers. Examples of greater access than is normally accessible by providers based on the need to know are access to sensitive information for which access typically requires a patient's consent. This is not an override of a patient's dissent to disclose sensitive information in cases where the applicable policy waives the need for that consent to access this information. In US, Title 38 Section 7332 and 42 CFR Part 2 both permit emergency access without the need to override a patient's consent directive; rather, this access is a limitation to the patient's right to dissent from disclosure.
ERTREAT | http://terminology.hl7.org/CodeSystem/v3-ActReason | emergency room treatment | To perform one or more operations on information for provision of immediately needed health care for an emergent condition in an emergency room or similar emergent care context by end users provisioned for this purpose, which does not constitute as policy override such as in a "Break the Glass" purpose of use. Map:Partially Maps to ISO 14265 Classification Term "Emergency care provision to an individual subject of care" described as "To inform persons needing to provide health care services to the subject of care urgently, possibly needing to over-ride the policies and consents pertaining to Purpose 1 above." Purpose 1 is equivalent to HL7 treatment purpose of use: "Clinical care provision to an individual subject of care" described as "To inform persons or processes responsible for providing health care services to the subject of care." The ISO description conflates both of the proposed specializations of HL7 ETREAT: break the glass and the typically broader access to health information normally available to providers who are provisioned for emergency workflows on a regular basis, e.g., Emergency Room providers. Examples of greater access than is normally accessible by providers based on the need to know are access to sensitive information for which access typically requires a patient's consent. This is not an override of a patient's dissent to disclose sensitive information in cases where the applicable policy waives the need for that consent to access this information. In US, Title 38 Section 7332 and 42 CFR Part 2 both permit emergency access without the need to override a patient's consent directive; rather, this access is a limitation to the patient's right to dissent from disclosure. There is a semantic gap in concepts. This classification term is described as activities "to inform persons" rather than the rationale for performing actions/operations on information related to the activity.
POPHLTH | http://terminology.hl7.org/CodeSystem/v3-ActReason | population health | To perform one or more operations on information for provision of health care to a population of living subjects, e.g., needle exchange program.
TREATDS | http://terminology.hl7.org/CodeSystem/v3-ActReason | decision support assisted treatment decision | To apply algorithms (e.g. AI, CDS) to perform one or more operations on information to arrive at decision used in health care treatment.
NZLEG | https://standards.digital.health.nz/ns/nz-purpose-of-use | legislative requirement | To perform actions otherwise described in New Zealand Legislation
NZRISK | https://standards.digital.health.nz/ns/nz-purpose-of-use | risk assessment | To perform risk management assessment and the disclosure is solely to a person engaged by the agency for the purpose of assessing the agency’s risk
NZCHILD | https://standards.digital.health.nz/ns/nz-purpose-of-use | child abuse reporting | To perform actions relating to the mandatory reporting of child abuse
NZSCREEN | https://standards.digital.health.nz/ns/nz-purpose-of-use | screening | To perform actions relating to screening carried out under legislation
NOTSUPPLIED | https://standards.digital.health.nz/ns/nz-purpose-of-use | No code supplied | Where no purpose of use code was supplied in an API request. This may not be a valid code for clients to supply, but will be used in the audit record to indicate no purpose of use code was included in a rejected request.

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