x QBOS REST API documentation for REMITBUNDLE

QBOS REST API documentation (REMITBUNDLE)

(return to Main Document)

Introduction

The REMITBUNDLE API allows client applications to maintain REMITBUNDLE 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}/...

REMITBUNDLE 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 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 3915 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.
Line_Number bigint Yes Yes NULL
Provider_Number nvarchar 20 Yes NULL
Number_Of_Claims bigint Yes Yes NULL
Total_Charge money Yes Yes NULL
HCPCS_Charge money Yes Yes NULL
HCPCS_Payable nvarchar 20 Yes NULL
Covered_Days bigint Yes Yes NULL
Noncovered_Days bigint Yes Yes NULL
Covered_Charge money Yes Yes NULL
Denied_Charge money Yes Yes NULL
Noncovered_Charge money Yes Yes NULL
Total_Adjustment money Yes Yes NULL
Total_Interest money Yes Yes NULL
Total_Payment money Yes Yes NULL

REMITBUNDLE Relationships

Parent and Child relations to REMITBUNDLE.

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_2352" : 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_2351 1-Many Yes Remittance_File
Parent Relations
↑
REMITBUNDLE
↓
Child Relations
Relation Id Cardinality
(Parent-to-Child)		 Required
**on POST of child		 Links Down To  
REL_2352 1-Many Yes** Remittance_Claim  
 



Read REMITBUNDLE by id:

GET https:/.../v1/517090/REMITBUNDLE/{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/REMITBUNDLE/127
Unauthorized request.

Read REMITBUNDLE by parent id:

GET https:/.../v1/517090/{parent_relation_id}/{parent_id}/links/REMITBUNDLE[?{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/0/506764/links/REMITBUNDLE
Unauthorized request.

Read REMITBUNDLE by filter:

GET https:/.../v1/517090/REMITBUNDLE[?{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/REMITBUNDLE?id=127
Unauthorized request.

Create REMITBUNDLE:

POST https:/.../v1/517090/REMITBUNDLE

Request data [See properties]:

Response codes:

Update REMITBUNDLE:

PUT https:/.../v1/517090/REMITBUNDLE/{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 REMITBUNDLE:

DELETE https:/.../v1/517090/REMITBUNDLE/{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 REMITBUNDLE:

POST https:/.../v1/517090/{relation_id}/{link_to_id}/links/REMITBUNDLE/{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 REMITBUNDLE:

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


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

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

Response codes:

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