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® profiles |
| Development principles | Page | High-level principles related to the development of the system |
| API design principles | Page | High-level design principles related to the API design |
| Non-functional requirements | Page | Details of non-functional requirements (NFRs) that describe system attributes such as security, reliability, maintainability, scalability, and usability (oft... |
| Security | Page | Details of the API security model and supported protocols |
| Volumetric and performance | Page | Details of the API volume and performance (V&P) characteristics |
| Branch surgeries | Page | Describes how GP Connect manages branch surgery data |
| Development deliverables | Page | Developer shortcuts for the technical build of GP Connect API |
| FHIR® implementation | Page | Implementation guidance for developers - focusing on FHIR® specifics |
| Error handling | Page | Details of the common error handling pattern(s) across the GP Connect API |
| FHIR® library | Page | There are benefits to using an existing FHIR® library |
| FHIR® resources | 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 |
| Interaction IDs | Page | A list of GP Connect API interaction IDs |
