...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| minLevel | 1 |
|---|---|
| maxLevel | 4 |
| outline | true |
| type | flat |
| separator | pipe |
ID
...
STD003 - AIDC for Patient Identification | STD004 - AIDC: Automatic Identification and Data Capture |
STD070 - Patient Identifiers for Identity Bands | STD064 - NHS Number |
ID | STD003 |
|---|---|
Name | |
External ID | DCB1077 |
Version | 0.1 |
Link to standard | |
Standard Type | Data Standard (NHS) |
Status | Draft |
Effective Date | TBC |
...
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 |
|---|---|
External ID | DAPB0108 |
Version | 0.1 |
Link to standard | |
Standard Type | Data Standard (NHS) |
Status | Draft |
Effective Date |
...
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 |
|---|---|
External ID | DCB0099 |
Version | 0.1 |
Link to standard | |
Standard Type | Data Standard (NHS) |
Status | Draft |
Effective Date |
...
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 |
|---|---|
External ID | ISB0149-02 |
Version | 0.1 |
Link to standard | |
Standard Type | Data Standard (NHS) |
Status | Draft |
Effective Date |
...
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 |