Capabilities with Interoperability Relationships
- Victoria Bussey
- Martin Perou
- Michael France
ID | R10 |
|---|---|
Version | 1.0.0 |
Type | Reference |
Â
Introduction
This page provides guidance to Suppliers to understand which interoperability requirements are associated with each Capability.
Some interdependencies between individual interface Standards exist. Creating a compliant implementation requires implementing all the required dependent interface Standards, as detailed in the 'Dependencies' column.
Note: this page is for guidance only and does not supersede what is mandated in the individual Capabilities and Standards. Suppliers need to comply with all of the requirements that are mandated by the Capability/Capabilities that the Supplier is offering.Â
Foundation Capabilities
Appointments Management - GP
Interoperability Requirement | Dependencies |
|---|---|
IM1 - Interface Mechanism Provider requirements (if offering all Foundation capabilities) | |
GP Connect Appointment Management (Provider requirements) | |
Consultation Management - GP
Interoperability Requirement | Dependencies |
|---|---|
IM1 - Interface Mechanism Provider requirements (if offering all Foundation capabilities) | |
Patient Information Maintenance - GP
Interoperability Requirement | Dependencies |
|---|---|
IM1 - Interface Mechanism Provider requirements (if offering all Foundation capabilities) | |
GP Connect Access Record HTML (Provider requirements) | |
GP Connect Access Record Structured (Provider requirements) | |
GP Connect Send Document (Receiver requirements) | |
GP Connect Update Record (Receiver requirements) | |
Prescribing
Interoperability Requirement | Dependencies |
|---|---|
IM1 - Interface Mechanism Provider requirements (if offering all Foundation capabilities) | |
Referral Management - GP
Interoperability Requirement | Dependencies |
|---|---|
IM1 - Interface Mechanism Provider requirements (if offering all Foundation capabilities) | |
Resource Management
Interoperability Requirement | Dependencies |
|---|---|
IM1 - Interface Mechanism Provider requirements (if offering all Foundation capabilities) |
Non-foundation capabilities
Appointments Management - Citizen
Interoperability Requirement | Dependencies |
|---|---|
IM1 - Interface Mechanism (Patient interface Consumer) | |
Communicate with Practice - Citizen
Interoperability Requirement | Dependencies |
|---|---|
IM1 - Interface Mechanism (Patient interface Consumer)Â |
Communication Management
Interoperability Requirement | Dependencies |
|---|---|
There may be dependencies for implementing this Standard, however, there are no Interoperability Standards within the Capabilities and Standards model that are dependents. |
Cross-organisation Appointment Booking
Interoperability Requirement | Dependencies |
|---|---|
GP Connect Appointment Management (Consumer requirements) |
Digital Diagnostics
Interoperability Requirement | Dependencies |
|---|---|
Medicines Optimisation
Interoperability Requirement | Dependencies |
|---|---|
GP Connect Access Record Structured (Consumer requirements) |
Prescription Ordering – Citizen
Interoperability Requirement | Dependencies |
|---|---|
IM1 - Interface Mechanism (Patient interface Consumer) | |
Unified Care Record
Interoperability Requirement | Dependencies |
|---|---|
Or
|
View Record - Citizen
Interoperability Requirement | Dependencies |
|---|---|
IM1 - Interface Mechanism (Patient interface Consumer) | |
Community Pharmacy Capabilities
Consultation Management - Community Pharmacy
Interoperability Requirement | Dependencies |
|---|---|
GP Connect Access Record Structured (Consumer requirements) | |
GP Connect Update Record (Sender requirements) | |
Referral Management - Community Pharmacy
Interoperability Requirement | Dependencies |
|---|---|