The following pages and posts are tagged with
Title | Type | Excerpt |
---|---|---|
Clinical terminologies | Page | Brief guidance on how clinical terminologies are expected to be used within GP Connect |
Specification versioning | Page | An overview of how the specification (and other technical assets) are versioned |
Assurance principles | Page | High-level design principles related to the assurance processes |
Data model principles | Page | High-level design principles related to the FHIR data modelling aspects of the system |
Development principles | Page | High-level principles related to the development of the system |
Open API design principles | Page | High-level design principles related to the open API design |
Non-functional requirements | Page | Details of NFRs that describe system attributes such as security, reliability, maintainability, scalability, and usability (often referred to as the “ilities”) |
Security guidance | Page | Details of the API security model and supported protocols |
Volumetric & performance | Page | Details of the API volume and performance characteristics |
Developer Cheat Sheet | Page | Developer Cheat Sheet shortcuts for the technical build of GP Connect APIs. |
FHIR API guidance | Page | Implementation Guidance for developers - focusing on FHIR specifics |
Error handling guidance | Page | Details of the common error handling pattern(s) across the GP Connect API |
FHIR library guidance | Page | There are benefits to using an existing FHIR library |
Operation guidance | Page | Details of which operations a FHIR server should expose to be a fully compliant GP Connect solution |
Resource guidance | Page | Where to find details of what resources and operations a FHIR server should expose to be a fully compliant GP Connect solution |
General API guidance | Page | Implementation guidance for developers - focusing on general API implementation guidance |