The following pages and posts are tagged with
| Title | Type | Excerpt |
|---|---|---|
| Implementation standards | Page | Overview of the common HTML view rendering guidance in relation to the Access Record capability |
| Layout guide | Page | Overview of the common HTML view layout guidance in relation to the Access Record capability |
| 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 non-functional requirements (NFRs) that describe system attributes such as security, reliability, maintainability, scalability, and usability (oft... |
| Security guidance | Page | Details of the API security model and supported protocols. |
| Volumetric and 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. |
| Common API guidance | Page | Details of the common request handling pattern(s) across all GP Connect FHIR APIs |
| Error handling guidance | Page | Details of the common error handling pattern(s) across all GP Connect FHIR APIs. |
| 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. |
| Interaction IDs | Page | A list of GP Connect API interaction IDs |
