Robust, configurable, extendible software

Our software development methodology extensively leverages Agile practices and test automation to achieve high velocity and high quality. The GO Precision Medicine Portfolio™ is developed on a single code base, designed so that our products are highly configurable and extendible. This is critical for serving our clients, who may have radically different requirements from one another. Our team will work with yours to document the high-level requirements and any work-flow or user interface changes. From there, our team will create detailed functional specifications, implement the changes along with the automated tests, test and then release the code when ready. The automated tests created for each new feature allow to us to guarantee the reproducibility of data analyses and interpretation even as we continue to extend the platform.

Biomedical informatics

At GenomOncology, we believe the most successful software platforms have domain expertise built in, from the ground up. Applying that philosophy, we have incorporated the use of several established ontologies. We’ve also written parsers and other utilities to achieve comprehensive cross-mapping of genetic concepts and diverse notations. Doing so makes it possible for our systems to recognize equivalent, overlapping, or nested descriptions of genetic variants and karyotypic elements. All of this is crucial for true decision support based on practice guidelines and for accurate clinical trial matching.

Integration with other systems

A common requirement from clients is compatibility and integration with existing systems. GenomOncology’s flagship product, the GO Clinical Workbench™ includes a middleware technology that addresses the three primary challenges of systems integration:

  • Transport: Our platform can communicate over a variant of protocols natively such as HTTP, HL7, FTP, SSH, etc.
  • Routing: Sending messages of different types to different end-points is easily configured.
  • Transformation: Messages can be changed from one format to another by writing pluggable transformers to convert between any 2 formats (e.g. XML to JSON, HL7 to CSV, etc.)

The image below provides an overview of integration architecture: