Non-admitted patient service event—non-admitted service type, code (Tier 2 v4.1) NN.NN
Data Element Attributes
Identifying and definitional attributes | |
Metadata item type:![]() | Data Element |
---|---|
Short name:![]() | Non-admitted service type |
METEOR identifier:![]() | 649490 |
Registration status:![]() |
|
Definition:![]() | The type of service through which an establishment provides health care to a non-admitted patient in a non-admitted setting, as represented by a code. |
Data Element Concept:![]() | Non-admitted patient service event—non-admitted service type |
Value domain attributes | |
Representational attributes | |
Classification scheme: | Tier 2 Non-Admitted Services classification (version 4.1) |
---|---|
Representation class:![]() | Code |
Data type:![]() | Number |
Format:![]() | NN.NN |
Maximum character length:![]() | 4 |
Collection and usage attributes | |
Guide for use:![]() | The code set is based on the list and definitions outlined in the document: Tier 2 Non-Admitted Services Definitions Manual (version 4.1). |
Source and reference attributes | |
Submitting organisation:![]() | Independent Hospital Pricing Authority |
Origin:![]() | Independent Hospital Pricing Authority 2016. Tier 2 Non-Admitted Services Definitions Manual. Independent Hospital Pricing Authority, Sydney. Viewed 23 August 2016, https://www.ihpa.gov.au/publications/tier-2-non-admitted-services-definitions-manual-2016-17 |
Data element attributes | |
Collection and usage attributes | |
Guide for use:![]() | The Non-admitted patient (NAP) data set is intended to capture instances of healthcare provision from the point of view of the patient. This may be for assessment, examination, consultation, treatment and/or education. One service event is recorded for each interaction, regardless of the number of healthcare providers present. Events broken in time: The period of interaction can be broken but still regarded as one service event if it was intended to be unbroken in time. This covers those circumstances in which treatment during a service event is temporarily interrupted for unexpected reasons, for example, a healthcare provider is called to assess another patient who requires more urgent care. Where a healthcare provider is unable to complete the interaction, it is considered to be a service event only if the definition of service event (above) is met. Setting: Service events can occur in an outpatient clinic or other setting. Mode: Service events delivered via Information and Communication Technology (ICT) (including but not limited to telephone and where the patient is participating via a video link) are included if:
Accompanied patients: If a patient is accompanied by a carer/relative, or the carer/relative acts on behalf of the patient with or without the patient present (e.g. the mother of a two-year-old patient, or the carer for an incapacitated patient), only the patient’s service event is recorded unless the carer/relative interaction meets the definition of a service event (above). Note: carer refers to an informal carer only. Service events delivered in groups: Care provided to two or more patients by the same service provider(s) at the same time can also be referred to as a group session. One service event is recorded for each patient who attends a group session regardless of the number of healthcare providers present, where the definition of a service event (above) is met. Service requests: A service event is the result of a service request (including formal referral and self-referral or attendance at a walk-in clinic). Activities which do not meet the definition of a service event include:
|
Source and reference attributes | |
Submitting organisation:![]() | Independent Hospital Pricing Authority |
Relational attributes | |
Related metadata references:![]() | Supersedes Non-admitted patient service event—non-admitted service type, code (Tier 2 v4.1) NN.NN
Has been superseded by Non-admitted patient service event—non-admitted service type, code (Tier 2 v5.0) NN.NN
|
Implementation in Data Set Specifications:![]() | Health, Superseded 25/01/2018 Implementation start date: 01/07/2017 Implementation end date: 30/06/2018 Health, Superseded 12/12/2018 Implementation start date: 01/07/2018 Implementation end date: 30/06/2019 Health, Superseded 25/01/2018 Implementation start date: 01/07/2017 Implementation end date: 30/06/2018 Health, Superseded 12/12/2018 Implementation start date: 01/07/2018 Implementation end date: 30/06/2019 Health, Superseded 25/01/2018 Implementation start date: 01/07/2017 Implementation end date: 30/06/2018 Health, Superseded 12/12/2018 Implementation start date: 01/07/2018 Implementation end date: 30/06/2019 |