Representation of the data
ITK3 is being used as the vehicle to transport the data between care settings, as it is well-established across GP and pharmacy system suppliers.
The representation, however, makes use of the GP Connect data model (FHIR STU3 representation) - which is the same model that is used by GP Connect - Access Record: Structured, and GP Connect - Patient Facing Services.
The intention is that the vehicle can be changed (for example, from ITK3 to a REST API) - but the FHIR profiles (outside of those required for ITK3) can still be ingested - rather than having to build new mappers to ingest data from the FHIR representation to the receiving system internal data model.
The initial use cases for this capability are pharmacy-based, and care has been taken to ensure that the fields within the PRSB Pharmacy Standard (V3.01) can be represented, without bespoke requirements on the FHIR representation that deviate from the existing profiles.
Each use case will be indicated via the appropriate SNOMED CT code using the Profile: CareConnect-Composition-1, within the type element.
Appropriate SNOMED CT codes
| Pharmacy Service | SCTID | Fully specified name | Suggested display name |
|---|---|---|---|
| Pharmacy Contraception Service | 1659121000000101 | Community Pharmacy Contraception Service (procedure) | Community Pharmacy Contraception Service |
| Hypertension Case Finding Service | 1659111000000107 | Community Pharmacy Blood Pressure Check Service (procedure) | Hypertension Case Finding Service |
| Pharmacy First (clinical pathways and minor illness) | 2129921000000100 | Community Pharmacy Pharmacy First Service (procedure) | Community Pharmacy Pharmacy First Service |