Placeholder page for GSRN implementation guidance.
Authors: Alexander Henket / Christian Hay
- Obtain OID for GSRN from GS1 -- done
- Register OID in HL7 OID Registry -- done
- Add OID in text here -- done
- Discuss how to integrate the SRIN (Service Relation Instance Number, which is an attribute to GSRN)
Suggested structure of the document:
A GSRN goes into the
<id/> attribute of the appropriate class, e.g. if the GSRN is used as a Patient identifier, then the GSRN goes into Patient.id. The OID for GSRNs is 184.108.40.206. The GSRN itself goes into @extension.
Preliminary text. This page is devoted to guide you on how to apply GSRN identifiers in HL7 V3. It may be updated to include FHIR
Background On GSRN
The Global Service Relation Number (GSRN) is the GS1 Identification Key used to identify the relationship between an organisation offering services (in this case, any Healthcare provider) and the recipient of services (in this case, the patient). The same Identification Key can be used to identify the relationship between the organisation offering the service and the provider of the service (in this case, the caregiver), but using a different Application Identifier to clearly distinguish the role. The data string is comprised of the:
- • Application Identifier, provides the meaning of the data field which follows, allowing the same GS1 data carrier to encode multiple data fields
- • GS1 Company Prefix, allocated by GS1 Member Organisations to member companies and users, enabling them to allocate GSRNs
- • Service Reference, allocated by the member company or user to each different person
- • Check Digit, provides extra security by preventing accidental key stroke errors
Use case #1 Subject of Care transferred from one Provider to another Provider: A badly burned SoC arrives in an emergency at Provider. Immediate care is provided and the admission process is completed. The SoC is issued with an identification band “1” containing an GSRN. Due to the SoC condition and needs, the SoC must be transferred to a specialised burns unit Provider. The specialised provider is informed of the SoC identification, the SoC’s condition and the care received before transfer. When the SoC arrives at the specialist Provider, the SoC’s identification band “1” is read to confirm the correct SoC and a new identification band issued by the specialist Provider.
Use case #2 Radiology process: The SoC is brought to the radiology department for an examination. The identification band has to be removed. After the examination and before the SoC leaves the radiology department a new band must be issued.
Use case #3 (chronic outpatient at home)
- When the medications are delivered to the home of the SoC, documenting the correct medications are supplied to the SoC at that right location, e.g. the fridge of the SoC. If recalled and/or expired medicinal products have been found, these are taken back.
- Selecting medicinal product: The SoC selects the medication from fridge, uses AIDC to scan their SCI, then the medication identifier (Global Trade Item Number, GTIN, and attributes such as lot number, expiry date and serial number) and registers the transaction removing the medication from the fridge. The scanner also checks the expiry date and ensures that the medication has not expired and checks for any recalled batches. Alerts are displayed on the scanner if either of these situations arises. If SoC is alerted, medicinal product is placed on a separate shelf and another medicinal product is selected.
- The SoC prepares and self-administers the medication, recording the administration event on the scanner. When SoC is a child, one parent is processing the medication. Additional clinical information can be captured such as the reason for treatment and other conditions experienced by the Patient.
HL7 V3 Fragments
Example XML fragments