Date: Fri, 29 Mar 2024 19:00:41 +1000 (AEST) Message-ID: <2059632010.1162.1711702842003@dsp-kbconf-01.ad.medicalobjects.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1161_121601642.1711702841998" ------=_Part_1161_121601642.1711702841998 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
There are several ways to integrate with Medical-Objects. We have many o= ptions for this, and obviously HL7 v2.3.1 is our preferred method of integr= ation. Our integration tool Medical-Objects Adapter Services is extremely p= owerful and we would strongly recommend this method of integration.
There are times however when the knowledge of HL7 is outside the boundar= ies of the development team and they need some simple methods of sending vi= a Medical-Objects. We have provided capabilities to integrate using several= methods which we will describe here.
HL7 = Messaging with Medical-Objects
Medical-Objects have an ActiveX control that can be used to create a cli= nical letter or report and send it through. In addition the library also al= lows for checking the online status of providers and the delivery status of= reports. Click here to view the ActiveX - COM+ Object Client example code
Medical-Objects provide a number of Web Services to call into to provide= a number of services. From SNOMED CT to Delivery and Status checking. We e= ncourage you to contact us wh= en using this service.
Medical-Objects provide a number of Rest based interfaces on its Caprico= rn systems which is useful to integrate with Click here for a .NET sending example<= /p>
Some interfaces will require certificates to secure the connection. For = information on how to generate certificates for this purpose see the Certificate = Wizard walk through.