x QBOS REST API documentation for PATINFO

QBOS REST API documentation (PATINFO)

(return to Main Document)

Introduction

The PATINFO API allows client applications to maintain PATINFO data record sets.

Audience

This developer's guide is intended for software developers needing a technical reference for using the QBOS REST API. The information you find in this guide is written by software engineering, and is authoritative on how the API behaves.

Additional resources, information about this guide

Occasionally, we make a mistake in this documentation, or unknowingly break a feature that you depend on. If this has happened to you, we apologize! You can help us fix the issue by contacting us at: pkajaani@qbos.com. We appreciate your help.

Getting Started

To place any request in a QBOS API application from a third party application you need to first authenticate your user account and set/calculate values for the following request headers: x-qbos-id, x-qbos-nonce, x-qbos-date-utc, x-qbos-hash-version, x-qbos-auth

See details in Authentication Documentation.

Custom resource vs. standard resource URI format

Custom resource (a.k.a applet) URI contains the resource vendor id in place of "/o/" in the standard object URI. Compare: .../v1/o/...with .../v1/{vendor_id}/...

PATINFO properties

Properties prefixed with '_' (underscore) are read-only properties. i.e. POST and PUT processing will ignore these properties.

Name Type Max
Length
Numeric Required
For POST
Filterable Computed
Column
Default Description
_client_Id bigint Yes NULL This is the Data Org Id.
_owner_Id bigint Yes Yes NULL This is the user id of the record owner. Defaults to the creatorOpid.
_creator_Opid bigint Yes Yes NULL This is the user id of the original record submitter.
_create_Date datetime No {timestamp}   Not enterable upon Insert. System sets this date upon record creation.
status_id int Yes Yes 2051 The status id of the record. Taken from the Life Cycle statuses in ADS.
_status_Change_Date datetime No NULL Not enterable. System sets this date whenever the statusid is changed.
Name nvarchar 60 No NULL
RF_Date datetime Yes NULL
RF_Caller_is_a_professional bit Yes No 0 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
RF_Assoc_to_Patient nvarchar 40 No NULL This property is populated by a Type 2 Value List.
Click here for the appropriate API and sample of value options for this column.
RF_Referring_Physician_Name nvarchar 80 Yes NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
RF_Aware_of_Referral nvarchar 1 No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
RF_How_did_you_hear_about_us nvarchar 80 Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
RF_Situation_Notes nvarchar(MAX) No NULL
RR_Followup_visit bit Yes No 0 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
RR_Registration_Rep_Id integer Yes No NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
RR_Registration_Rep_Date datetime No NULL
RR_Visit_Location_Notes nvarchar(MAX) No NULL
RR_Provider_Relations nvarchar 50 No NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
RR_Previously_under_Hospice_care bit Yes Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
RR_Transferred_from_another_Hospice bit Yes Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
RR_Name_of_Other_Hospice nvarchar 80 No NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
CG_Primary_Caregiver nvarchar 60 Yes NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
CG_Secondary_Caregiver nvarchar 60 Yes NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
CG_Power_of_Attorney nvarchar 20 Yes NULL
PD_Sex bit Yes No 1 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
PD_Marital_Status integer Yes No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
PD_Ethnicity nvarchar 25 No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
PD_Religion nvarchar 30 No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
PD_Is_A_Veteran bit Yes No 0 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
PD_Funeral_Home nvarchar 80 No NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
PD_Funeral_Home_Address nvarchar(MAX) No NULL
Show integer Yes No 1 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
GN_Admission_Status integer Yes Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
_Patient_Age integer Yes No Yes =DATEDIFF(Y,Patient_DOB ,today )
AD_Admit_Date datetime Yes NULL
PI_NOE_complete bit Yes No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
Print_Facesheet bit Yes No 0 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
Billing_Hold_and_Release integer Yes Yes 1 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
Hold_Billing_Reason nvarchar(MAX) No NULL
SF_Attending_Physician nvarchar 50 No NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
SF_Team nvarchar 20 No NULL This property is populated by a Type 2 Value List.
Click here for the appropriate API and sample of value options for this column.
SF_Admit_RN nvarchar 50 No NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
SF_RN_CM nvarchar 50 No NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
SF_Aide nvarchar 50 No NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
SF_Social_Worker nvarchar 50 No NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
SF_Chaplain nvarchar 50 No NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
SF_Bereavement nvarchar 50 Yes NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
SF_Nurse_Practitioner nvarchar 50 Yes NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
SF_Nurse_Liaison nvarchar 50 Yes NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Physician_Order integer Yes No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Eval bit Yes No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Eval_Date_and_Time datetime No NULL
AD_Aware_of_diagnosis integer Yes No NULL This property is populated by a Type 2 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Aware_of_prognosis integer Yes No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Attending_Physician nvarchar 60 Yes NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Certifying_Physician nvarchar 60 Yes NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Terminal_Diagnosis nvarchar 255 Yes NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Skilled bit Yes No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Related_to_Terminal_Diagnosis bit Yes No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Skilled_end_date datetime No NULL
AD_DNR bit Yes No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Full_Code bit Yes No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_DPOA_Proxy bit Yes No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Living_Will bit Yes No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_DNRCC bit Yes No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Advance_Directive bit Yes No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Pharmacy nvarchar 60 No NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Pharmacy_phone nvarchar 10 No NULL
AD_Pharmacy_fax nvarchar 10 No NULL
GN_Followup_Date datetime Yes NULL
GN_Followup_Notes nvarchar(MAX) No NULL
Patient_SSN nvarchar 9 Yes NULL
Patient_DOB datetime Yes NULL
CG_Primary_Caregiver_Phone nvarchar 10 No NULL
CG_Primary_Caregiver_Address nvarchar(MAX) No NULL
CG_Secondary_Caregiver_Phone nvarchar 10 No NULL
CG_Secondary_Caregiver_Address nvarchar(MAX) No NULL
CG_Primary_Caregiver_Relation nvarchar 40 No NULL This property is populated by a Type 2 Value List.
Click here for the appropriate API and sample of value options for this column.
CG_Secondary_Caregiver_Relation nvarchar 40 No NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
RR_Benefits_Assigned bit Yes No 1 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
Patient_Age_Alpha nvarchar 3 No NULL
AD_EOB_Requested bit Yes No 0 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
Chart_Billing_Status integer Yes Yes 1 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
Send_Referral_Email bit Yes Yes 0 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
Show_Last_Admit_Date datetime Yes NULL
On_Hold_Recert bit Yes Yes 0 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
On_Hold_F2F bit Yes Yes 0 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
CG_Primary_Caregiver_Name nvarchar 25 Yes NULL
RF_Referral_Type nvarchar 20 Yes Pat_Ref_Email This property is populated by a Type 2 Value List.
Click here for the appropriate API and sample of value options for this column.
Caller_Type nvarchar 40 Yes Guardian This property is populated by a Type 2 Value List.
Click here for the appropriate API and sample of value options for this column.
add_rf_physician bit Yes Yes 0 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_DPOA_proxy_upload bit Yes Yes 0 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
RR_Phone_of_Other_Hospice nvarchar 15 Yes NULL
RR_From_Date_of_Other_Hospice datetime Yes NULL
RR_End_Date_of_Other_Hospice datetime Yes NULL
Patient_Current_Benefit_Period integer Yes Yes NULL
Patient_First_Lang integer Yes Yes NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
Curr_Loc_Same_Pat_Address bit Yes Yes 0 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
Care_Loc_Same_Pat_Address bit Yes Yes 0 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
Care_Loc_Same_Curr_Loc bit Yes Yes 0 This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
Patient_Current_Location_Type nvarchar 50 Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
Patient_Care_Location_Type nvarchar 50 Yes NULL
Patient_Caregiver_Type nvarchar 50 Yes NULL This property is populated by a Type 2 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Code_Status nvarchar 50 Yes NULL This property is populated by a Type 2 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Secondary_Terminal_Diagnosis nvarchar 255 Yes NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Co_Morbid_Cond nvarchar 50 Yes NULL This property is populated by a Type 3 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Skilled_Bed_Rem_Days integer Yes Yes NULL
RF_Doctors_Orders nvarchar 20 Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
RF_Doctors_Action_Orders nvarchar 20 Yes NULL This property is populated by a Type 2 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Billing_Diagnosis nvarchar 50 Yes NULL
Patient_Status nvarchar 40 Yes NULL This property is populated by a Type 2 Value List.
Click here for the appropriate API and sample of value options for this column.
CAL_Assoc_to_Patient nvarchar 50 Yes NULL This property is populated by a Type 2 Value List.
Click here for the appropriate API and sample of value options for this column.
RF_Credit nvarchar 25 Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
RF_CreditContactName nvarchar 80 Yes NULL
Patient_TypeOfCare nvarchar 20 Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_Certification_AllRecordsObtained bit Yes Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
Verified_Physician nvarchar 20 Yes NULL
PD_HospiceLocation nvarchar 50 Yes NULL
RF_Ordering_Physician_Name nvarchar 20 Yes NULL
RF_Ordering_Person_Name nvarchar 20 Yes NULL
RC_Assoc_to_Patient nvarchar 20 Yes NULL This property is populated by a Type 2 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_CareLocation_SameAsCurrent bit Yes Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
AD_DNRCCA bit Yes Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
RF_Signed_Orders nvarchar 20 Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
OtherCaregiverNote nvarchar 200 Yes NULL
PrimaryCaregiverNote nvarchar 2500 Yes NULL
RR_All_Records_Obtained nvarchar 20 Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
RR_ROI_Consent_Given nvarchar 20 Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
Allow_Cahps_Publication bit Yes Yes NULL This property is populated by a Type 1 Value List.
Click here for the appropriate API and sample of value options for this column.
Patient_Gender nvarchar 1 Yes NULL
RiskPriority nvarchar 20 Yes NULL
Carelocation_Timezone nvarchar 20 Yes NULL
New_Patient_Chart_ID bigint Yes Yes 0

PATINFO Relationships

Parent and Child relations to PATINFO.

Note that the only Required status on relationships that affect a POST of an object are on the parent relations. A Required status on a child relation is only meaningful when POSTing the child object.

Linking during POST: a custom object record can be linked to a parent or child record (custom or standard) during POST by including (in the payload) the realtion id paired with the parent or child object record being linked to. For example: { "REl_2904" : 1832 }      Multiple links may be created in the same POST.

Relation Id Cardinality
(Parent-to-Child)
Required
For POST
Links Up To Is Unary?*
REL_1496 1-Many Contact
REL_3153 1-Many Care_Team
REL_2911 1-Many Physician_Info
REL_2909 1-Many Contact
REL_2908 1-Many Contact
REL_2907 1-Many Contact
REL_2906 1-Many Contact
REL_2903 1-Many Physician_Info
REL_1735 1-Many Contact
REL_1571 1-Many Contact
Parent Relations

PATINFO

Child Relations
Relation Id Cardinality
(Parent-to-Child)
Required
**on POST of child
Links Down To  
REL_2904 1-1 Yes** Contact  
REL_2905 1-1 Yes** Contact  
REL_2910 1-Many Yes** Contact  
REL_1652 1-Many Yes** Admit_Nurse_Visit  
REL_2537 1-Many Yes** Physician_Certification  
REL_1653 1-Many Yes** Patient_Level_of_Care  
REL_1658 1-Many Yes** Payor_Information  
REL_2566 1-Many Yes** Billing_Coverage_Matrix  
REL_1666 1-Many Yes** Service_Periods  
REL_1756 1-Many Yes** Claim_Items  
REL_2538 1-Many Yes** Face-To-Face_visits  
REL_2846 1-Many PharmScript  
REL_2894 1-Many Yes** Hospice_itemSet_2014  
REL_2898 1-Many Yes** Patient_Ref_Aware  
REL_2536 1-Many Yes** Patient_Billed_Claims  
REL_1573 1-Many Yes** Patient_Visit  
REL_2943 1-Many CA_Assessment  
REL_3157 1-Many Yes** CP_IDGREVIEW  
REL_3143 1-Many Yes** PatientChart_Notes  
REL_3139 1-Many Yes** HIS_Admission_Info  
REL_3154 1-Many Yes** HIS_Discharge_Info  
REL_3155 1-Many Yes** Patient_CoMorbids  
REL_3179 1-Many Yes** Patient_Payer_Info  
REL_3222 1-Many Yes** Patient_Symptoms_Reasons  
REL_3228 1-Many Yes** F2FSummaryLabAndNarr  
REL_3229 1-Many Yes** F2FAttestation  
REL_3254 1-Many Person_Ethnicity  
REL_3263 1-Many POC_Issue  
REL_3283 1-Many Patient_Medication  
REL_3284 1-Many Patient_Allergy  
REL_3286 1-Many Yes** CA_Supervisory_Visit  
REL_3288 1-Many Yes** CP_VISITFREQUENCY  
REL_3125 1-Many Yes** Care_Team_Patient  
REL_3140 1-Many Yes** DIAGNOSIS_HISTORY  
REL_3142 1-Many Patient_IDG_VISITS  
REL_3279 1-Many IDG_Meeting_Patient  
REL_3218 1-Many Yes** Discipline_Visits  
REL_3221 1-Many Yes** AssessmentNarratives_Continuous  
REL_3245 1-1 CP_POC_HOSPICIDE  
REL_3089 1-Many Yes** CP_POC_Issue  
REL_3250 1-Many CP_POC_VISITFREQUENCY  
REL_1734 1-Many Yes** Nurse_Visit  
REL_2913 1-Many PAT_CARE_GIVER  
REL_3275 1-Many Assessment_Issue  
REL_2900 1-Many Attending_Physician_Info  
REL_3238 1-Many Notes  
 



Read PATINFO by id:

GET https:/.../v1/517090/PATINFO/{id}

Response codes:

  • 200 - OK
  • 404 - Not found or user does not have permission to access resources of this type.
  • 400 - Client error
  • 500 - Server error

Response data: GET https:/.../v1/517090/PATINFO/1
Unauthorized request.

Read PATINFO by parent id:

GET https:/.../v1/517090/{parent_relation_id}/{parent_id}/links/PATINFO[?{filter}]

Response codes:

  • 400 - Client error
  • 500 - Server error
  • 404 - Not found or user does not have permission to access resources of this type.
  • 200 - OK

Response data: GET https:/.../v1/517090/1496/507001/links/PATINFO
Unauthorized request.

Read PATINFO by filter:

GET https:/.../v1/517090/PATINFO[?{filter}]

Response codes:

  • 200 - OK
  • 400 - Client error
  • 404 - Not found or user does not have permission to access resources of this type.
  • 500 - Server error

Response data: GET https:/.../v1/517090/PATINFO?id=1
Unauthorized request.

Create PATINFO:

POST https:/.../v1/517090/PATINFO

Request data [See properties]:

Response codes:

Update PATINFO:

PUT https:/.../v1/517090/PATINFO/{id}

Request data [See properties]:

Response codes:

  • 200 - OK Content returned [See response data]
  • 204 - OK No content
  • 400 - Client error
  • 404 - Not found
  • 500 - Server error

Delete PATINFO:

DELETE https:/.../v1/517090/PATINFO/{id}

The "id" in JSON payload is required to match the {id} in the URI to ensure that deletion requests are intended and safe

Response codes:

  • 204 - OK
  • 400 - Client error
  • 404 - Not found
  • 500 - Server error

Create Link for PATINFO:

POST https:/.../v1/517090/{relation_id}/{link_to_id}/links/PATINFO/{id}


{relation_id} can indicate either a parent or a child relation.

Response codes:

  • 204 - OK
  • 400 - Client error
  • 404 - Not found
  • 500 - Server error

Delete Link for PATINFO:

DELETE https:/.../v1/517090/{parent_relation_id}/{parent_id}/links/PATINFO/{id}


Deleting a link from PATINFO down to a child object must be explicitly indicated by negating the relation id:

DELETE https:/.../v1/517090/{-child_relation_id}/{child_id}/links/PATINFO/{id}

Response codes:

  • 204 - OK
  • 400 - Client error
  • 404 - Not found
  • 500 - Server error