API & Web Services

Dynamic Health IT (DHIT) offers custom API and web service development. Both APIs and Web services use open standards to exchange data. An API provides parameters for how software components can interact with an application. Our API development enables any web development language to access the API. Web services are Web based applications that XML-based standards and transport protocols to exchange data between two electronic devices. There are two major classes of Web Services including the REST-compliant Web services and the arbitrary Web services. WSDL is an XML language that is used to describe the functionality of a Web service and SOAP is a protocol specification for exchanging structured information in the implementation of Web services. DHIT can leverage development we’ve done for other clients and projects, including:


DHIT implemented OAuth - an open standard for authorization via third-party applications - via a web-based API, enabling wider, secure communication to the Dr. Chrono EHR.


ePrescribing for DoseSpot and Surescripts using a Web services client. The Web service client interfaces Vendor EHR Systems to the Surescripts E-Prescription Network. It supports sending e-prescriptions to pharmacies nationwide, routing refill requests from pharmacies to the physician EMR, and handling approval/denial of refills by physicians. This application requires minimal work on the part of the vendor since it handles all interactions with the SureScripts network.


DHIT created a Web service client application -based on the WSDL description- that can communicate with the Care360 Hub Information Services Web services. The Client application helped to retrieve lab results data in HL7 format from Quest and to store them in Vendor’s database.


DHIT created a Web service server application to exchange data securely between a Third-Party Vendor application and PCC. The vendor chose to host the Certified Vendor Partner application in their own infrastructure. Pushing transmission method is used to transmit data in which the sending system calls the recipient system whenever there is data to transmit and then transmits that data. The difference between Polling and Pushing is which party initiates the communication.
With Pushing method, PCC will initiate the message pushing process once a message was added to the partner’s outbound queue. This will trigger the PCC system to send a SOAP Request to the partner’s system. Once the partner’s system accepts, authenticates, preprocesses and parses the SOAP request, it will send a synchronous acknowledgment to the PCC system. The PCC system will then process this acknowledgment.


Transmission of Immunization records to state agencies, secured by X509 certificate over SSL during transmission.

web service graph