Provincial Client Registry (PCR) HL7 FHIR® Contribution Implementation Guide v1.0.0-draft1
For a full list of available versions, see the Directory of published versions
The Batch Transaction Submission business use case enables a Contributor to submit multiple patient transactions for processing within a single batch. The batch may contain patient create, patient update, and patient merge requests.
PCR validates the batch submission and processes each transaction according to applicable patient identity management, governance, stewardship, duplicate prevention, and survivorship policies. Individual transactions within the batch are evaluated independently and may result in successful processing, rejection, or routing for stewardship review.
The process supports efficient high-volume patient identity management activities while maintaining patient identity integrity, auditability, lineage preservation, source attribution, and compliance with approved governance requirements.
Contributor submits a batch transaction request containing one or more patient create, patient update, and patient merge transactions.
Positive Scenario PCR successfully processes the batch submission. New patient identities are created where appropriate, existing patient records are updated, duplicate patient records are merged, audit information is recorded, and processing results are returned to the Contributor.
**Alternative Positive Scenario ** PCR successfully processes valid transactions within the batch while rejecting or deferring transactions that fail validation or require stewardship review. Processing results are provided for each transaction.
Negative Scenario The batch submission is rejected when authorization, governance, message validation, or operational requirements cannot be satisfied. Audit information is recorded and the Contributor is notified of the reason for rejection.
POST: Patient Batch Submission
Actor: Contributor
Role: Submits a Bundle of Create/Update/Merge submissions to the PCR.
Actor: PCR Role: Receives, authenticates, validates, and stores incoming patient information from the Contributor.
Patient Batch Submission Request
Patient Batch Submission Request
The batch interaction is performed by an HTTP POST command as shown:
POST [base-submit]/
Patient Batch Submission Response
Patient Batch Submission Response
| Outcome | Header HTTP Response | Payload OperationOutcome |
|---|---|---|
| Batch interaction processed | 200 OK | Yes |
| Validation failure | 400 Bad Request or 422 Unprocessable Entity | Yes |
| Contributor not authorized | 401 Unauthorized or 403 Forbidden | No |
| Processing failure or service unavailable | 5xx Server Error | No |