HSAAP Special Authority FHIR Implementation Guide
0.1.1 - draft
HSAAP Special Authority FHIR Implementation Guide - Local Development build (v0.1.1) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
An Application is enquired by its business identifier, the Application Number. The resources are the same Claim and
ClaimResponse used for Submit Application, so a retrieved Application and a submitted one
share one shape.
The Application record is mutable. Enquiry always reflects the Application's current state; prior states cannot be
retrieved. Retrieval by FHIR resource id (GET [base]/Claim/[id]) is not supported.
All identifier searches SHALL be system-qualified (system|value). See Identifiers and Naming Systems.
GET [base]/Claim?identifier=https://fhir-ig.digital.health.nz/special-authority/ns/application-number|{applicationNumber}
&_include=Claim:patient
&_include=Claim:requestor
&_include=Claim:supportinginfo
The _include parameters resolve the full shape produced at submission - Claim, QuestionnaireResponse, Patient and
Practitioner - so a retrieval and a submission return structurally identical content. Claim:requestor is a custom
search parameter that resolves to the Applicant in Claim.provider (see Design Notes).
On retrieval, Claim.identifier carries the Application Number, and asserted source context is returned in the
submission-context extension. The stored source payload is never returned.
GET [base]/ClaimResponse?request.identifier=https://fhir-ig.digital.health.nz/special-authority/ns/application-number|{applicationNumber}
&_elements=extension,preAuthRef
Returns an SA Application ClaimResponse whose
application-status extension carries the same status, outcome,
outcomeCode and outcomeReason returned synchronously at submission (D22). preAuthRef carries the Approval Number
where the Application was approved. _elements limits the response to the status and Approval Number.
existing-approval is not returned on enquiry. A conflicting Approval is resolved at submission, so that detail is
only useful in the immediate response.
Example: pending review.
GET [base]/Claim?identifier={application-number-system}|{applicationNumber}
GET [base]/Claim?patient.identifier=https://standards.digital.health.nz/ns/nhi-id|{nhi}
GET [base]/Claim?requestor:Practitioner.identifier=https://standards.digital.health.nz/ns/hpi-person-id|{cpn}
GET [base]/Claim?requestor:Practitioner.identifier=https://standards.digital.health.nz/ns/medical-council-id|{registrationNumber}
GET [base]/Claim?application-status=PENDING_REVIEW
GET [base]/Claim?created=ge2026-01-01&created=le2026-01-31
| Parameter | Definition | Notes |
|---|---|---|
identifier |
core | Application Number system only. |
patient.identifier |
core, chained | NHI. |
requestor:Practitioner.identifier |
claim-requestor, chained | Supply either the HPI CPN or a registration identifier. The registration authority is the identifier system (e.g. Medical Council), the registration number the value. |
application-status |
application-status | SUBMITTED, PENDING_REVIEW, CANCELLED, DONE. Claim.status cannot express these. |
created |
core | ge / le map to submitted-from and submitted-to. |
Filters may be combined. Search results are summary representations: referenced Patient, Practitioner,
Organization and QuestionnaireResponse resources are not resolved. Use
Retrieve a submitted Application for full detail.
GET [base]/ClaimResponse?identifier=https://fhir-ig.digital.health.nz/special-authority/ns/approval-number|{approvalNumber}
&_include=ClaimResponse:request
The Approval Number is an adjudication result, so it is carried on ClaimResponse, never on Claim (D23). The
_include returns the originating Claim in the same response.