# Update site zimbis patient profile

Endpoint: PUT /site/{siteId}/zimbis/patient/{siteZimbisPatientId}/profile/{siteZimbisPatientProfileId}
Version: 1.0
Security: bearer

## Path parameters:

  - `siteId` (number, required)

  - `siteZimbisPatientId` (number, required)

  - `siteZimbisPatientProfileId` (number, required)

## Request fields (application/json):

  - `siteId` (number, required)
    The ID of the site associated with this Patient
    Example: 1.23

  - `patientId` (string, required)
    Patient identifier - the Account ID in 3rd party system
    Example: "123e4567-e89b-12d3-a456-426614174000"

  - `fhirId` (string, required)
    The ID of the FHIR Patient associated with this patient
    Example: "123e4567-e89b-12d3-a456-426614174000"

  - `ehrId` (string, required)
    The ID of the record in ehr system
    Example: "123e4567-e89b-12d3-a456-426614174000"

  - `ehrTable` (string, required)
    The Table name of the record in ehr system
    Example: "Example Name"

  - `zimbisPatientId` (number, required)
    The id of the related zimbis patient table record
    Example: 1.23

  - `profileId` (string, required)
    Profile identifier/medication order number
    Example: "123e4567-e89b-12d3-a456-426614174000"

  - `newDiscontinued` (number, required)
    0 = New, new profiles are ready to be dispensed to a patient - 1 = Discontinued, discontinued profiles will appear at the cabinet to be dispensed to a patient
    Example: 1.23

  - `itemId` (string, required)
    Unique identifier for the item to be dispensed, typically provided by the practice management software
    Example: "123e4567-e89b-12d3-a456-426614174000"

  - `description1` (string, required)
    Description of the drug or supply to be dispensed, this is typically the brand name of the drug
    Example: "Example Name"

  - `description2` (string, required)
    Second description of the drug or supply to be dispensed this is typically a generic equivalent of the drug
    Example: "Example description"

  - `profileQTYReq` (number, required)
    The quantity of the drug or supply to be dispensed at each occurrence, e.g. if a profile specified 1 2mg tablet of Valium to be dispensed 3 times, this value would be 1
    Example: 1.23

  - `issueDAU` (string, required)
    The unit to be issued, e.g. Each
    Example: "example"

  - `occurrences` (number, required)
    The number of times the drug or supply is to be accessed for a patient before the profile is inactive
    Example: 1.23

  - `giveStrength` (number, required)
    The strength of the drug or supply to be dispensed, e.g. if a profile specified 1 2mg tablet of Valium to be dispensed 3 times, the GiveStrength would be 2
    Example: 1.23

  - `giveStrengthUnit` (string, required)
    The unit to be dispensed, e.g. mg or cc
    Example: "example"

  - `chargeCode` (string, required)
    Charge code
    Example: "CODE-001"

  - `schedule` (string, required)
    The date and time the drug or supply will be available to be given to the patient, this must be in the time zone of the dispensing cabinet
    Example: "Example Name"

  - `endDate` (string, required)
    The date and time the drug or supply will be discontinued, this must be in the time zone of the dispensing cabinet, when left blank the system will default to the Schedule date and time + 100 years
    Example: "example"

  - `bid` (string, required)
    Dispensing instructions in abbreviations
    Example: "example"

  - `instructions` (string, required)
    Freeform field to capture any extra information about the drug to be dispensed or the manner in which it is to be dispensed
    Example: "example"

  - `id` (number, required)
    The ID of the site Zimbis Patient Profile to be updated
    Example: 100

  - `createdAt` (string, required)
    The date and time the data record was created
    Example: "2021-08-01T00:00:00.000Z"

  - `updatedAt` (string, required)
    The date and time the data record was last updated
    Example: "2021-08-01T00:00:00.000Z"

  - `syncedAt` (string, required)
    The date and time the data record was last synced
    Example: "2021-08-01T00:00:00.000Z"

## Response 200 fields (application/json):

  - `siteId` (number, required)
    The ID of the site associated with this Patient
    Example: 1.23

  - `patientId` (string, required)
    Patient identifier - the Account ID in 3rd party system
    Example: "123e4567-e89b-12d3-a456-426614174000"

  - `fhirId` (string, required)
    The ID of the FHIR Patient associated with this patient
    Example: "123e4567-e89b-12d3-a456-426614174000"

  - `ehrId` (string, required)
    The ID of the record in ehr system
    Example: "123e4567-e89b-12d3-a456-426614174000"

  - `ehrTable` (string, required)
    The Table name of the record in ehr system
    Example: "Example Name"

  - `zimbisPatientId` (number, required)
    The id of the related zimbis patient table record
    Example: 1.23

  - `profileId` (string, required)
    Profile identifier/medication order number
    Example: "123e4567-e89b-12d3-a456-426614174000"

  - `newDiscontinued` (number, required)
    0 = New, new profiles are ready to be dispensed to a patient - 1 = Discontinued, discontinued profiles will appear at the cabinet to be dispensed to a patient
    Example: 1.23

  - `itemId` (string, required)
    Unique identifier for the item to be dispensed, typically provided by the practice management software
    Example: "123e4567-e89b-12d3-a456-426614174000"

  - `description1` (string, required)
    Description of the drug or supply to be dispensed, this is typically the brand name of the drug
    Example: "Example Name"

  - `description2` (string, required)
    Second description of the drug or supply to be dispensed this is typically a generic equivalent of the drug
    Example: "Example description"

  - `profileQTYReq` (number, required)
    The quantity of the drug or supply to be dispensed at each occurrence, e.g. if a profile specified 1 2mg tablet of Valium to be dispensed 3 times, this value would be 1
    Example: 1.23

  - `issueDAU` (string, required)
    The unit to be issued, e.g. Each
    Example: "example"

  - `occurrences` (number, required)
    The number of times the drug or supply is to be accessed for a patient before the profile is inactive
    Example: 1.23

  - `giveStrength` (number, required)
    The strength of the drug or supply to be dispensed, e.g. if a profile specified 1 2mg tablet of Valium to be dispensed 3 times, the GiveStrength would be 2
    Example: 1.23

  - `giveStrengthUnit` (string, required)
    The unit to be dispensed, e.g. mg or cc
    Example: "example"

  - `chargeCode` (string, required)
    Charge code
    Example: "CODE-001"

  - `schedule` (string, required)
    The date and time the drug or supply will be available to be given to the patient, this must be in the time zone of the dispensing cabinet
    Example: "Example Name"

  - `endDate` (string, required)
    The date and time the drug or supply will be discontinued, this must be in the time zone of the dispensing cabinet, when left blank the system will default to the Schedule date and time + 100 years
    Example: "example"

  - `bid` (string, required)
    Dispensing instructions in abbreviations
    Example: "example"

  - `instructions` (string, required)
    Freeform field to capture any extra information about the drug to be dispensed or the manner in which it is to be dispensed
    Example: "example"

  - `id` (number, required)
    The ID of the site Zimbis Patient Profile to be updated
    Example: 100

  - `createdAt` (string, required)
    The date and time the data record was created
    Example: "2021-08-01T00:00:00.000Z"

  - `updatedAt` (string, required)
    The date and time the data record was last updated
    Example: "2021-08-01T00:00:00.000Z"

  - `syncedAt` (string, required)
    The date and time the data record was last synced
    Example: "2021-08-01T00:00:00.000Z"

## Response 401 fields (application/json):

  - `message` (string, required)
    Error message indicating unauthorized access.
    Example: "Unauthorized"

  - `statusCode` (number, required)
    HTTP status code for unauthorized access.
    Example: 401


## Response 400 fields