SET.API.Services

<back to all web services

ReferralDetailsGetRQ

The following routes are available for this service:
GET/RisingIntegration/ReferralDetails/{ReferralId}
ReferralDetailsGetRQ Parameters:
NameParameterData TypeRequiredDescription
ReferralIdpathGuidNo
SETReferralDetailsDTO Parameters:
NameParameterData TypeRequiredDescription
SETReferralNumberformstringNo
ClaimantFirstNameformstringNo
ClaimantLastNameformstringNo
ClaimantInitialsformstringNo
ClaimNumberformstringNo
DateOfServiceformstringNo
StatusformstringNo
TransportTypeformintNo
LanguageformstringNo
MedicalScheduleTypeIdformintNo
MedicalScheduleTypeformstringNo
ServiceTypeDescriptionformstringNo
RisingReferralNumberformstringNo

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 /RisingIntegration/ReferralDetails/{ReferralId} 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

<SETReferralDetailsDTO xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/SET.API.Services.ServiceModel.RisingIntegration">
  <ClaimNumber>String</ClaimNumber>
  <ClaimantFirstName>String</ClaimantFirstName>
  <ClaimantInitials>String</ClaimantInitials>
  <ClaimantLastName>String</ClaimantLastName>
  <DateOfService>String</DateOfService>
  <Language>String</Language>
  <MedicalScheduleType>String</MedicalScheduleType>
  <MedicalScheduleTypeId>0</MedicalScheduleTypeId>
  <RisingReferralNumber>String</RisingReferralNumber>
  <SETReferralNumber>String</SETReferralNumber>
  <ServiceTypeDescription>String</ServiceTypeDescription>
  <Status>String</Status>
  <TransportType>0</TransportType>
</SETReferralDetailsDTO>