Create a Test Patient

Test Patient Requirements

Test patient demographics must support consistent matching evaluation across multiple submissions.

Use demographics that meet the following criteria:

• Realistic but non-production values
• Complete demographic attributes, including first name, last name, date of birth, gender, and address
• Stable values reused across all submissions and test cycles

Demographic variation across submissions may result in multiple patient matches and interfere with shareback validation.

Create a Patient in the Patient360 UI

Using the Patient360 UI, you can manually create a patient for shareback testing. Manual patient creation supports validation of UI-based shareback workflows and visibility of submitted data within the Patient360 interface.

To enter the patient demographics:

1. On the Home page, click Create Patient.
2. Enter the patient demographics using realistic, non-production values.
3. Select Save.

To upload a patient document:

1. On the left, in the Create New menu, select CCD Document.
2. On the New CCD Document page, click Select File and add the document.
3. When the file is loaded, click Save.

Once created, the Patient ID serves as the anchor for all subsequent clinical data submissions.

Create a Patient using FHIR APIs

System-to-system workflows support patient creation through Health Gorilla FHIR APIs. Patient creation through APIs follows the same matching evaluation logic used by the Patient360 UI.

1. Obtain an OAuth 2.0 access token with permission to create patient resources.
2. Submit a Patient resource to the sandbox FHIR endpoint using an HTTP POST request.
3. Include complete demographic attributes in the request payload, including name, date of birth, gender, and address.
4. Verify that the request returns a 201 Created response.
5. Capture the Patient ID from the Location response header.

Use this request to create the test patient that anchors all subsequent shareback submissions. Capture and reuse the returned Patient ID consistently.

Example Request

POST https://sandbox.healthgorilla.com/fhir/R4/Patient

Example Body

{
    "resourceType": "Patient",
    "name": [
        {
            "use": "usual",
            "text": "Nathaniel Robert Caldwell",
            "family": "Caldwell",
            "given": [
                "Nathaniel",
                "Robert"
            ],
            "suffix": [
                "Sr"
            ]
        }
    ],
    "address": {
        "text": "518 Oak Ridge Ave, Knoxville, TN 37917",
        "line": [
            "518 Oak Ridge Ave"
        ],
        "city": "Knoxville",
        "state": "TN",
        "postalCode": "37917",
        "country": "US"
    },
    "gender": "female",
    "birthDate": "1959-03-12",
    "identifier": [
        {
            "type": {
                "coding": [
                    {
                        "system": "http://terminology.hl7.org/CodeSystem/v2-0203",
                        "code": "SB",
                        "display": "Social Beneficiary Identifier"
                    }
                ],
                "text": "Social Beneficiary Identifier"
            },
            "system": "http://hl7.org/fhir/sid/us-ssn",
            "value": "456-78-9013"
        }
    ],
    "telecom": [
        {
            "system": "email",
            "value": "[email protected]"
        },
        {
            "system": "phone",
            "value": "5557891234",
            "use": "home"
        },
        {
            "system": "phone",
            "value": "5557891235",
            "use": "work"
        },
        {
            "system": "phone",
            "value": "5557891236",
            "use": "mobile"
        }
    ],
    "maritalStatus": {
        "coding": [
            {
                "system": "http://terminology.hl7.org/CodeSystem/v3-MaritalStatus",
                "code": "D",
                "display": "Divorced"
            }
        ],
        "text": "Divorced"
    }
}

Example Response Header

HTTP/1.1 201 Created
Location: https://sandbox.healthgorilla.com/fhir/R4/Patient/{patientId}

Patient Matching During Testing

Patient matching occurs before clinical data is associated with a patient record.

During sandbox testing:

• Demographic mismatches may result in creation of a new patient record.
• Minor demographic differences may prevent association with an existing patient record.
• Stable, consistent demographics improve predictable shareback readiness results.

Patient matching behavior during testing reflects production evaluation rules but does not result in live data exchange with external organizations.