MediBuddy Mobile Services V1.1

HospitalDoctorDetailsRequest

The following routes are available for this service:
POST	/hospital/getdoctordetails/

To override the Content-type in your clients 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.

POST /xml/reply/HospitalDoctorDetailsRequest HTTP/1.1 
Host: mb-mobile-api.medibuddy.in 
Content-Type: application/xml
Content-Length: length

<HospitalDoctorDetailsRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobile.DTO.RequestResponse">
  <IPAddress xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobileAPI.Core.DTO">String</IPAddress>
  <MBToken xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobileAPI.Core.DTO">String</MBToken>
  <MobileDeviceModel xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobileAPI.Core.DTO">String</MobileDeviceModel>
  <PlatformVer xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobileAPI.Core.DTO">String</PlatformVer>
  <UserAgent xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobileAPI.Core.DTO">String</UserAgent>
  <UserPlatform xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobileAPI.Core.DTO">String</UserPlatform>
  <HospitalId>0</HospitalId>
</HospitalDoctorDetailsRequest>

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

<HospitalDoctorDetailsResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/MediBuddyMobile.DTO.RequestResponse">
  <DoctorDetails xmlns:d2p1="http://schemas.datacontract.org/2004/07/MediBuddyMobile.DTO">
    <d2p1:NetworkHospitalDoctorDetails>
      <d2p1:ContactNo>String</d2p1:ContactNo>
      <d2p1:DoctorDepartmentID>0</d2p1:DoctorDepartmentID>
      <d2p1:DoctorDepartments xmlns:d4p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
        <d4p1:string>String</d4p1:string>
      </d2p1:DoctorDepartments>
      <d2p1:DoctorExperience>String</d2p1:DoctorExperience>
      <d2p1:DoctorImage>String</d2p1:DoctorImage>
      <d2p1:DoctorName>String</d2p1:DoctorName>
      <d2p1:DoctorOPDTimings>
        <d2p1:Timings>
          <d2p1:InTime>PT0S</d2p1:InTime>
          <d2p1:OutTime>PT0S</d2p1:OutTime>
        </d2p1:Timings>
      </d2p1:DoctorOPDTimings>
      <d2p1:DoctorQualification>String</d2p1:DoctorQualification>
      <d2p1:DoctorRegNo>String</d2p1:DoctorRegNo>
      <d2p1:DoctorTimingsString>String</d2p1:DoctorTimingsString>
      <d2p1:DoctorType>String</d2p1:DoctorType>
      <d2p1:EmailId>String</d2p1:EmailId>
      <d2p1:HospId>0</d2p1:HospId>
      <d2p1:HospName>String</d2p1:HospName>
      <d2p1:Id>0</d2p1:Id>
    </d2p1:NetworkHospitalDoctorDetails>
  </DoctorDetails>
</HospitalDoctorDetailsResponse>