The following pages and posts are tagged with
| Title | Type | Excerpt |
|---|---|---|
| HTML Implementation Guide | Page | Overview of the common HTML view rendering 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 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. |
| 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. |
| Open Source Guidance | Page | Details of open source FHIR libraries. |
| 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. |
