J2EE ARCHITECTURE DESIGN

development platforms should be based on Java EE and the following tools and frameworks provide a better indication of the specific technical aspects of the application: • Authentication: Token based - JWT tokens • Contextual search database: ElasticSearch • Development platform: Spring framework • Transport layer security: SSL Signed Certificate • Relational database: PostgreSQL or similar • Services API: RESTful web services (with options to support SOAP and other standards where applicable) • Messaging: JMS • Object versioning: Envers or similar • Web client: Single page javascript framework such as Vue or AngularJS 4 The goal for the proposed architecture is to create a system that encapsulates all relevant and complimentary medical coding data as well as coding rules into a service that is uniformly available, secure and scalable. The system should support multiple tenants with various licensing and usage agreements. The system should provide access to all features and codes or only a subset of features and codes based on the end user agreement and licensing model. The system should expose a fully featured user interface allowing users to use the system as a cloud based service (SaaS) as well as expose various APIs for integration. The system should allow for the centralized administration of codes (and possibly, the configuration of coding rules depending on complexity and timelines) The system should have high availability and facilitate seamless upgrades and updates. The system should allow access to coding rule documentation based on context. (PDF documentation and help functionality) Optionally, a feedback loop, which records and analyses previously captured data, would greatly improve usability of the system and create a ‘self learning’ system that is able to predict and guide a user to the correct coding.