Creating high-technology value solutions, Delivering reliable services

Web Services

Service Oriented Architecture (SOA)
A Web Service is a flexible data exchange solution that is fully compatible with SOA infrastructures. BayaTree supports inbound “published” services, as well as outbound “message” depending on the particular level of use which can be inserted where needed throughout the application. The result is a system that is far more interoperable and configurable. This might allow for the retirement of other legacy systems that have held you hostage for many years, or it may make it possible to interface with them. The end result might be superior performance with less IT overhead in terms of products to support, annual support fees, and IT headaches. Projects can move rapidly through the implementation process in which, and the old standard still holds true, time is money. So, in selecting a product, understand how the vendor plans development of their product, not just what functions it is capable of fulfilling.


  • Expose functionality in a service-oriented world
  • Create a standard object model for BayaTree products and services
  • Support transformation of object models to a variety of external standard data models (CDISC, HL7 v3.0)
  • Support a variety of standard integration technologies (HL7 v2, SOAP, REST, JMS, etc.)
  • Provide administrative functionality to allow for monitoring and maintenance of deployed services

Service API
A centralized Service API serves as the basis for both incoming and outgoing services, regardless of format or protocol. This Service API includes the following features:

  • Adherence to standard Software Patterns wherever feasible
  • Consistent – an entity is an entity, no matter what application is accessing it
  • Support transformation of object models to a variety of external standard data models (CDISC, HL7 v3.0)
    • Changes are discouraged, but documented in release notes
    • Methods are deprecated for several releases rather than removed
    • Java Docs are distributed with every release
  • A common object model to be used for a variety of applications
  • Published Web Service
  • Message-based integration
  • Other services
  • Plug-ins
  • API supports added plug-ins

A set of standard services are developed to include all of the major areas of application functionality within the interoperability framework. Messaging services allow for messages to be sent to external parties based on pre-defined trigger events.

Extension APIs
For all services, the framework is delivered with the core set of modules. An extension API is made available to investigate incoming and outgoing messages for the purposes of customization.

The owner of this website has made a commitment to accessibility and inclusion, please report any problems that you encounter using the contact form on this website. This site uses the WP ADA Compliance Check plugin to enhance accessibility.