The following pages and posts are tagged with
| Title | Type | Excerpt |
|---|---|---|
| Access Record Structured design | Page | Overview of the design decisions made in relation to the Access Record Structured capability |
| Development overview | Page | Development overview to the Access Record Structured capability |
| Allergies guidance | Page | Guidance on the representation of allergies and intolerances in GP Connect |
| AllergyIntolerance resource | Page | Guidance for populating and consuming the AllergyIntolerance resource |
| Bundle | Page | Guidance for populating and consuming the Bundle resource |
| FHIR® Allergies examples | Page | Access Record Structured FHIR examples |
| Forward compatibility support examples | Page | Access Record Structured FHIR examples |
| FHIR® Medication examples | Page | Access Record Structured FHIR examples |
| List | Page | Guidance for populating and consuming the List resource |
| Medication resource | Page | Guidance for populating and consuming the Medication resource |
| Medication guidance | Page | Guidance on the representation of medication in GP Connect |
| Medication resource relationships | Page | Representation of medication processes using FHIR® profiles in GP Connect |
| MedicationRequest resource | Page | Guidance for populating and consuming the MedicationRequest resource |
| MedicationStatement resource | Page | Guidance for populating and consuming the MedicationStatement resource |
| FHIR® resources overview | Page | List of FHIR resource profiles used in the Access Record Structured capability pack |
| Retrieve a patient's structured record | Page | Retrieve a patient's record in structured format |
| API Version Compatibility | Page | API Version Compatibility |
| Known issues | Page | Known issues related to the Access Record Structured capability pack |
| Design decisions | Page | Overview of the design decisions made in relation to the Appointment Management capability pack |
| Known issues | Page | Known issues related to the Appointment Management capability |
| Appointment Management service discovery | Page | Determining which GP practices to book into |
| Wireframes | Page | Wireframe mock-ups of what GP Connect Appointment Management might look like in a consumer application |
| Clinical terminologies | Page | Brief guidance on how clinical terminologies are expected to be used within GP Connect |
| Design decisions | Page | Overview of the design decisions made in relation to the Foundations capability pack |
| Foundations known issues | Page | Known issues related to the Foundations capability |
| Foundations wireframes | Page | Wireframe mock-ups of what GP Connect Foundations might look like when used in a consumer application |
