SET.API.Services

DentalTreatmentPlanLineItemsGetByAppointment

The following routes are available for this service:
GET	/Dental/Appointment/{AppointmentId}/TreatmentPlanLineItems

**DentalTreatmentPlanLineItemsGetByAppointment** Parameters:
Name	Parameter	Data Type	Required	Description
AppointmentId	path	string	No

**DentalTreatmentPlanLineItem** Parameters:
Name	Parameter	Data Type	Required
Id	form	string	No
TreatmentPlanId	form	string	No
ADACode	form	string	No
ADACodeDescription	form	string	No
ICD10Code	form	string	No
ICD10CodeDescription	form	string	No
ToothNumber	form	int	No
SurfaceCode1	form	string	No
SurfaceCode2	form	string	No
Units	form	int	No
APCharged	form	decimal	No
APDiscount	form	decimal	No
ARTotal	form	decimal	No
ARDiscount	form	decimal	No
APPaidStatus	form	string	No
ARPaidStatus	form	string	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

GET /Dental/Appointment/{AppointmentId}/TreatmentPlanLineItems HTTP/1.1 
Host: set-api-service-prod.azurewebsites.net 
Accept: application/xml

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<DentalTreatmentPlanLineItem xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/SET.API.Services.ServiceModel.Types">
  <ADACode>String</ADACode>
  <ADACodeDescription>String</ADACodeDescription>
  <APCharged>0</APCharged>
  <APDiscount>0</APDiscount>
  <APPaidStatus>String</APPaidStatus>
  <ARDiscount>0</ARDiscount>
  <ARPaidStatus>String</ARPaidStatus>
  <ARTotal>0</ARTotal>
  <ICD10Code>String</ICD10Code>
  <ICD10CodeDescription>String</ICD10CodeDescription>
  <Id>String</Id>
  <SurfaceCode1>String</SurfaceCode1>
  <SurfaceCode2>String</SurfaceCode2>
  <ToothNumber>0</ToothNumber>
  <TreatmentPlanId>String</TreatmentPlanId>
  <Units>0</Units>
</DentalTreatmentPlanLineItem>