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
Patient Create provides a RESTful approach to establishing a new Patient's Record within PCR based on demographic and identifying information submitted by a Contributor. In a Patient Create request, patient information is provided to PCR, which validates the submission and evaluates the data against existing managed patient identities using identity resolution, duplicate prevention, and source authority rules. PCR assesses the likelihood that the submitted information corresponds to an existing patient and applies governance policies to determine whether a new identity should be created or whether an existing identity should be referenced.
In the PCR Patient Create operation, the request must include a Patient resource populated with the information known about the individual being registered. The completeness and quality of the information provided directly influence PCR's ability to accurately evaluate potential matches and prevent duplicate patient creation. If no existing Patient's Record is determined to represent the individual, PCR creates a new Patient's Record, records the source contribution, and establishes the patient record in accordance with approved identity management, stewardship, and auditability requirements.
NOTE: FHIR's Conditional Create is not allowed at this time.
POST: Patient Create
Actor: Contributor
Role: Submits a Patient Contribution resource to the PCR.
Actor: PCR
Role: Receives, authenticates, validates, and stores incoming patient information from the Contributor.
The FHIR IR specification is based on the HL7 FHIR R4 Create operation.
Patient Create Request
The create interaction is performed by an HTTP POST command as shown:
POST [base-submit]/Patient/
Patient Create Response
Example Create Patient Request
HTTP Method:
POST
Headers:
Content-Type: application/fhir+json
Address:
[base-submit]/Patient/
Message Body:
Example Validation Failure
HTTP Response: 400 Bad Request
Message Body:
Example Duplicate or Conflict Condition
HTTP Response: 409 Conflict
Message Body:
| Outcome | Header HTTP Response | Payload OperationOutcome |
|---|---|---|
| Patient successfully created | 201 Created | Yes (Created Patient resource returned) |
| Existing patient identified and duplicate prevention rules applied | 200 OK or policy-specific outcome | Yes |
| Validation failure | 400 Bad Request | Yes (Validation details and expression path returned where applicable) |
| Contributor not authorized | 401 Unauthorized or 403 Forbidden | No |
| Duplicate prevention conflict | 409 Conflict | No (Business-rule confict details for contributor remediation returned) |
| Processing failure or service unavailable | 5xx Server Error | No |