...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Note |
|---|
This page has been superseded and archived. |
STD003 - AIDC for Patient Identification | STD004 - AIDC: Automatic Identification and Data Capture |
STD070 - Patient Identifiers for Identity Bands | STD064 - NHS Number |
ID | STD003 |
|---|---|
Name | AIDC for Patient Identification |
External ID | DCB1077 |
Version | 0.1 |
Link to standard | |
Standard Type | Data Standard (NHS) |
Status | Alpha |
Effective Date | TBC |
Description
This standard supports the accurate, timely and safer identification of NHS patients in England, by using barcodes for positive patient identification.
Automatic Identification and Data Capture (AIDC) for Patient Identification defines how to encode the NHS approved patient identifiers into the GS1 DataMatrix barcode (a two-dimensional barcode) and covers production, verification and printing rules for the barcode.
Applicability
This standard applies to all healthcare settings in England where an identity band is worn by the patient. It also applies to all healthcare IT systems used by the NHS in England that develop and implement systems which result in the production of patient identity bands.
This standard needs to be reviewed and implemented alongside the current AIDC Fundamental Standard ISB 0108: AIDC: Automatic Identification and Data Capture and its related standards and guidance outlined in Sections 1.2 and 1.3.
Requirements
Requirement ID | Requirement Text | Level |
|---|---|---|
STD003-1 | GS1 Compliance (Existing Users) For hospitals/healthcare providers that are already using ISB 1077 compliant wristbands with a GS1 DataMatrix barcode, the related Change Specification should be reviewed to ensure all changes are understood and can be implemented as specified. | SHOULD |
STD003-2 | GS1 Compliance (New Users) New users wishing to implement DCB1077 must ensure the information standard is reviewed alongside the ISB 0108: AIDC: Automatic Identification and Data Capture standard. Additionally, new users must review the “GS1 DataMatrix Guideline: Overview and technical introduction to the use of GS1 DataMatrix” to ensure all systems and equipment used to create the barcode is compliant with GS1 Standards. See section 6 of the Implementation Guidance for further information on technical requirements. | MUST |
ID | STD004 |
|---|---|
Name | AIDC: Automatic Identification and Data Capture |
External ID | DAPB0108 |
Version | 0.1 |
Link to standard | |
Standard Type | Data Standard (NHS) |
Status | Alpha |
Effective Date |
Description
DAPB0108 is an information standard developed by GS1 UK and endorsed by NHS via NHS England and NHS Improvement sponsor and NHS Digital SRO.
Applicability
NHS settings in England where Automatic Identification and Data Capture (AIDC) technologies (i.e. barcodes and RFID tags) are used as enablers to improve patient safety, ensure greater clinical effectiveness and drive operational efficiencies.
Requirements
Requirement ID | Requirement Text | Level |
|---|---|---|
STD004-1 | Compliance to GS1 Standards To be compliant with DAPB0108, is to be compliant to any relevant GS1 Standards, which means that the AIDC system or product being procured, deployed, and used. | MUST |
STD004-2 | GS1 Identification keys Utilise GS1 Identification keys for the required data elements based on the functionality and purpose of the system being considered. | MUST |
STD004-3 | GS1 Data Carriers Produce, print, and read GS1 Data Carriers such as barcodes or EPC/RFID tags, in accordance with the specifications provided for the intended application. | MUST |
STD004-4 | Data Format/Carriers Whilst system design and business processes around collections and data flow remain out of scope for DAPB0108, health IT systems may need to be modified to ensure the data format and data carrier requirements specified can be complied with. The safety implications of any such modifications must be considered by manufacturers of health IT systems as well as those involved in the deployment and use of health IT systems. | MAY |
ID | STD070 |
|---|---|
Name | Patient Identifiers for Identity Bands |
External ID | DCB0099 |
Version | 0.1 |
Link to standard | |
Standard Type | Data Standard (NHS) |
Status | Alpha |
Effective Date |
Description
This information standard specifies both the four identifiers that must be included on NHS patient identity bands and the format for presenting them, so that identity information is clear and unambiguous to all healthcare staff. A well-designed identity band, based on this standard, reduces the risk of mis-identification, helping to ensure a patient is not given the wrong care and treatment.
Applicability
This standard applies to all healthcare settings in England where an identity band is worn by the patient. It also applies to all healthcare IT systems used by the NHS in England that develop and implement systems which result in the production of patient identity bands.
Requirements
Requirement ID | Requirement Text | Level |
|---|---|---|
STD0070-1 | Core Identifiers Supplier systems MUST contain the four core identifiers that uniquely identify a patient when used in combination and which must be present on the identity band are: Last Name, First Name (LASTNAME, firstname) Date of Birth (DD/MM/YYYY) Verified NHS Number (3 3 4 format, see NHS Number for full details) | MUST |
MAY
ID | STD064 |
|---|---|
NHS Number | |
External ID | ISB0149-02 |
Version | 0.1 |
Link to standard | |
Standard Type | Data Standard (NHS) |
Status | Alpha |
Effective Date |
Description
The aim of the NHS Number for Secondary Care standard ) is to increase NHS Number usage within Trusts, ensuring that the patient is correctly associated with their unique NHS Number.
Applicability
All information systems supporting the commissioning or provision of NHS Services that hold patient/service user demographic data.
• All information systems supporting the commissioning or provision of health and care services that are used to transfer or otherwise communicate patient/service user information with other bodies that commission or provide health and care services in England in partnership with the NHS.
• All new information systems procured after this standard comes into force. • All existing information systems where it is reasonably practicable, given cost and other constraints, to upgrade it to comply with this standard.
• All existing or new information systems where the use of the NHS Number would not compromise patient/service user care nor provide a barrier to the uptake of care services – this to be determined by a local clinical risk assessment
Requirements
Requirement ID | Requirement Text | Level |
|---|---|---|
STD0064-1 | Verification Status Applicable Systems must record the verification status of each recorded NHS Number. A verified NHS number has been cross-checked using demographic details on the Personal Demographics Service (PDS) | MUST |
STD0064-2 | Electronic Communication Only verified NHS numbers should be sent electronically | SHOULD |
STD0064-3 | Hard Copy Output Only verified NHS numbers should be be used when sending a hard copy output | SHOULD |