Life Sciences Cloud Developer Guide
No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
Action Plan Context Filters Input
Action Plan Template Input
Action Plan Template Item Filters Input
Appointed Representative Input
Assessment Links Input
Book Slot Chain Input
Build Identity Verification Context Input
Care Request Case Input
Care Request Patient Input
Care Authorization Request Input
Care Diagnosis Input
Care Request Drug Input
Care Request Input
Care Request Item Input
Care Requests List Input
Care Request Reviewer Input
Care Request Subscriber Input
Content Document Input
Create Visit Request Input
Custom Field Value Input
Digital Verification Input
Digital Verification Input Fields Map
Dispenser Address Input
Document Management Input
Document Process Input
Enrollee Product Input
Fields Without Conflict Input
FHIR Address Input
FHIR Codeable Concept Input
FHIR Codeable Concept Or ID Input
FHIR Coding Input
FHIR Contact Point Input
FHIR Dispense Input
FHIR Dosage Input
FHIR Dose
FHIR Dose And Rate
FHIR Human Name Input
FHIR Identifier Input
FHIR Medication Statement
FHIR Medication Resource Input
FHIR Patient Input
FHIR Rate
FHIR Reference Input
FHIR Request
First Reviewer Input
FHIR Unit Of Measure
FHIR Unit Of Measure Or ID
General Practitioner Input
Medical Director Input
Original Denial Medical Director Input
Patient Contact Party Input
Page Specification Input
Page Specification List Input
Patient Communication Language Input
Patient Input
Product Required Attributes Input
Program Enrollment Input
Slot Input
Reopened By Input
Requesting Practitioner Input
Servicing Facility Input
Servicing Practitioner Input
Search Input
Transport Location Input
User Credentials Input
Visited Party Attributes Input
Visitor Attributes Input
Work Type Lead Time Input
API End-of-Life Policy
Request Bodies
This section lists the request bodies for Life Sciences Cloud Business APIs. The query
parameters for an endpoint are listed along with each resource.
To create a JSON request body, specify the properties of the request body in JSON format. If a request body is top-level, it has a root XML tag listed. To create an XML request body, nest the properties as XML tags inside the root XML tag.
-
Action Plan Context Filters Input
Input representation of the action plan context filters. -
Action Plan Template Input
Input representation of an action plan template. -
Action Plan Template Item Filters Input
Input representation of the action plan template item filters. -
Appointed Representative Input
Person who is the appointed representative for the member. -
Assessment Links Input
Associated assessments including id, category, reason and sequence. -
Book Slot Chain Input
Input representation of the request to create service appointments. -
Build Identity Verification Context Input
Input representation of the Build Identity Verification Context resource. -
Care Request Case Input
Case related to the care request. -
Care Request Patient Input
The patient for whom the request is being raised. -
Care Authorization Request Input
A complete care authorization request. -
Care Diagnosis Input
Associated diagnosis including code type, name, and description. One or more care diagnoses can be associated with a care request. -
Care Request Drug Input
Requested drug including name, strength, frequency, and instructions for administration. One or more drug requests can be associated with a care request. -
Care Request Input
The general details of a care-related request including member information, admission date, decision reason, and so on. A single request can contain multiple diagnoses or drugs. Care requests include prior authorizations for drugs and services, admission notifications, concurrent review of admissions, appeals, complaints, and grievances. -
Care Request Item Input
The details of a care service request, including name, modifiers, and the effective date. One or more care service requests can be associated with a care request. -
Care Requests List Input
A list of care authorization requests. -
Care Request Reviewer Input
The general details of the care request, care request item, care request drug, or care diagnosis associated with the care request reviewer. -
Care Request Subscriber Input
The primary member on the plan. -
Content Document Input
Input representation for documents linked to the care request record. -
Create Visit Request Input
Input representation of the create visit request. -
Custom Field Value Input
Adds additional information to any fields not mapped by the medication statement API. -
Digital Verification Input
Input representation of the request to perform verification tasks for digital verification records. -
Digital Verification Input Fields Map
Input representation of the key-value pairs containing the fields to be updated for the digital verification. -
Dispenser Address Input
Address of the pharmacy. -
Document Management Input
Input representation for the document split request. -
Document Process Input
Input representation of the content document or received document record to create or update a Salesforce object record. -
Enrollee Product Input
Data for a single enrollee product. -
Fields Without Conflict Input
Input representation of the list of fields without conflict for record creation. -
FHIR Address Input
Input representation for the Address FHIR object. -
FHIR Codeable Concept Input
Input representation for the CodeableConcept FHIR object. -
FHIR Codeable Concept Or ID Input
Input representation for FHIR Codeable Concept or ID. -
FHIR Coding Input
Input representation for the Coding FHIR object. -
FHIR Contact Point Input
Input representation for the ContactPoint FHIR object. -
FHIR Dispense Input
The input representation of FHIR Dispense. -
FHIR Dosage Input
The input representation of dosage information for a patient’s medication. -
FHIR Dose
Input representation for the dosage quantity. -
FHIR Dose And Rate
Input representation of the specified dose and rate. -
FHIR Human Name Input
The input representation for the name of a person and all its associated metadata. -
FHIR Identifier Input
The input representation of the Identifier FHIR object. -
FHIR Medication Statement
Input representation for the Medication Statement FHIR object. -
FHIR Medication Resource Input
The input representation of FHIR Medication. -
FHIR Patient Input
Input representation for the FHIR patient resource. -
FHIR Rate
Input representation for dosage rate. -
FHIR Reference Input
The input representation for the Reference FHIR object. -
FHIR Request
Input representation for the supply of medication, along with information about how it should be administered. -
First Reviewer Input
The name of the person who reviewed the request. -
FHIR Unit Of Measure
Input representation for Unit of Measure. -
FHIR Unit Of Measure Or ID
Input representation for Unit of Measure Or Id. -
General Practitioner Input
Member's primary or general care practitioner. -
Medical Director Input
Name of the medical director who reviewed the request. -
Original Denial Medical Director Input
The name of the medical director who denied the original request. -
Patient Contact Party Input
The input representation of the patient contact party. -
Page Specification Input
Input representation of the page specification details. -
Page Specification List Input
Input representation of the page specification list. -
Patient Communication Language Input
Input representation of the patient communication language. -
Patient Input
Input containing data for a single patient. -
Product Required Attributes Input
Input representation of the products required for the visit. -
Program Enrollment Input
Request body for care program enrollment. -
Slot Input
Input representation of an appointment slot. -
Reopened By Input
The name of the person who reopened the care request. -
Requesting Practitioner Input
Ordering or referring practitioner for the request. -
Servicing Facility Input
Facility where the service is being provided. -
Servicing Practitioner Input
Practitioner administering the service. -
Search Input
Input representation for Search API -
Transport Location Input
Input representation for Transport Location -
User Credentials Input
Input representation of the user credentials to perform digital verification. -
Visited Party Attributes Input
Input representation of the visiting party. For example, for a medical device visit, the visiting party can be the surgeon and the anesthesiologist. -
Visitor Attributes Input
Input representation of the visitor attributes. For example, for a medical device visit, visitor can be the sales representative and the clinical specialist. -
Work Type Lead Time Input
Input representation of the request to get a list of work types and their associated lead times.