NZ Shared Digital Health Record API
0.4.0 - draft
NZ Shared Digital Health Record API
0.4.0 - draft
NZ Shared Digital Health Record API - Local Development build (v0.4.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
| NZ Shared Digital Health Record API |
NZ Shared Digital Health Record API |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| SDHRAllergyIntolerance |
AllergyIntolerance FHIR resource for Shared Digital Health Record |
| SDHRCondition |
Condition resource to record problems and conditions affecting a person |
| SDHRConsent |
Consent resource created to reflect a patient has agreed to share their information with authorised health workers, originating from a practice management system For more detail on how this resource is used, see the consent based access control page. |
| SDHREncounter |
Encounter resource to record an instance of an interaction between patient and healthcare provider |
| SDHRObservation |
A Shared Digital Health Record Observation. |
These define sets of codes used by systems conforming to this implementation guide.
These define new code systems used by systems conforming to this implementation guide.
| NZ-specific terminology for Shared Digital Health Records |
This system defines standard codes used throughout this Implementation Guide for New Zealand Shared Digital Health Records |
| SDHR Codes where the appropriate code is not known or can not be determined. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| APIError-Confidential |
Example OperationOutcome API response, returned when a resource has been flagged as confidential, and so cannot be accessed. |
| APIError-Unauthorised |
Access to Shared Digital Health Records is restricted.<br>
This API validates information that is provided by the API Consumer in their |
| AllergyIntoleranceExample |
An example payload for a Primary Care AllergyIntolerance resource indicating an allergy to Penicillin, with a confidentiality of restricted. |
| AllergyIntoleranceExample2 |
An example payload for a Primary Care AllergyIntolerance resource indicating an allergy to Cashew nuts |
| ConditionSearchResponseExample |
Example of a search response for a condition search. In this case the search response returns one result using the search parameters |
| ConfidentialRecordsSearchResponseExample |
Example of a searchset API response for an AllergyIntolerance resource search. In this case, the search response returns one entry item, with a total count of 2. This is because the API will not return the confidential record. The redacted security label is applied to the Bundle response, to indicate that confidential records have been removed from the result set. See the API documentation for more information. |
| HypertensionConditionExample |
Example Hypertension Condition |
| ObservationVitalSignsExample |
An example SDHR Vital Signs Observation |
| RespiratoryConditionExample |
Example Respiratory Condition |
| SDHRConsentExample |
Consent example submitted to allow a patient to opt in to sharing their information, originating from a practice management system |
| SDHREncounterExample |
Example Encounter resource to record an instance of an interaction between patient and healthcare provider |