Switch view side scroll on
  • Service ArchitectureThe Service Architecture includes the interfaces, middleware and backend systems which allow services to be delivered to customers.
    • BackendBackend provides software services and systems that run on a hosted server based system.
      • Backend SystemsBackend Systems are enterprise wide systems that support both the middleware and backend.
        • Enterprise Messaging System (EMS)The Enterprise Messaging System enables messaging between applications and systems, it provides loosely coupled asynchronous data (messages) to be sent by one program and stored in a message queue until the receiving program is able to process it.
        • Enterprise Service Bus (ESB)The Enterprise Service Bus implements a communication system between mutually interacting software applications in a service-oriented architecture (SOA).
        • Content Management System (CMS)The Content Management System is a computer application that supports the creation and modification of digital content.
        • Database Management System (DBMS)The Database Management System is the software that allows a computer to perform database functions of storing, retrieving, adding, deleting and modifying data.
        • Search EngineThe Search Engine is software that searches for and identifies items in a database that correspond to keywords or characters specified by the user.
        • Form EngineThe Form Engine provides software for creation of dynamic on-line forms.
      • Backend ServicesBackend Services are individual services that are combined to build business services.
        • Message ValidationMessage Validation provides the ability to validate a message format based on a standard profile.
        • Identity and Access Management (IAM)IAM refers to a framework of policies and technologies for ensuring that users have the appropriate access to business services.
        • Vendor ValidationVendor Validation provides a suite of tools for validating a vendors compliance with the interface standards.
        • Message TransformationMessage Transformation provides the ability to translate one message format to another, using the healthcare messaging standards.
        • Message CapabilityMessage Capability provides the ability to lookup a receiving systems ability to handle a message.
        • Advanced TrackingAdvanced Tracking records all health message activity , including the ability to track whether a message was accepted.
        • Data DictionaryThe Data Dictionary provides access to the form data model and view layout for all customer forms to ensure consistency a standard set of data concepts is defined along with basic validations.
        • Document HubDocument Hub allows uploading and downloading of documents to enable document collaboration.
        • Submission RouteThe Submission Route provides synchronous connectivity to a configurable submission endpoint.
        • Form Config / DesignerThe Forms Config provides the ability to configure the data model and view layout of the customers form.
        • CoreCore is the centralised repository of all databases merged into one.
        • Message QueueMessage Queue provides the ability to create individual customer message queues for sending and receiving messages.
    • InterfaceThe Interface provides the software interfaces between end users and user applications.
      • Forms InterfaceThe Forms Interface is used for exchanging information between the users application and the form.
        • AduroThis Aduro interface is provided by EMR vendors in Australia and is consumed by HealthLink forms for pre-population, saving forms to the EMR, re-opening submitted form and request other EMR activity.
        • HisoThis HISO interface is provided by EMR vendors in NZ and is consumed by HealthLink forms for pre-population, saving forms to the EMR, re-opening submitted form and request other EMR activity.
        • Form UIThe Form User Interface (UI) is a browser based user interface embedded within the users application which provides interaction with forms using web browser based controls.
        • Forms API / SDKForms API is a simple wrapper for both the Aduro and Hiso API clients.
        • Submission Gateway (SG)The Submission Gateway Interface allows form submission data to be sent to a common gateway.
      • Messaging InterfaceA Messaging Interface enables application programs to send and receive messages in a consistant manner independent of the transport.
        • File DropThe File Drop Interface provides a file system based interface for sending and receiving messages. This includes a standard directory folder structure, with sub folders for different message formats.
        • Message ExchangeMessage Exchange provides a web service interface. It is a symmetric interface (both ways) for exchanging messages with a set of metadata that declares the message type so that the recipient can validate.
      • Directory InterfaceThe Directory Interface allows the users to locate directory based information on the network.
      • Portal InterfaceThe Portal Interface is used for exchanging information between the users application and the portal.
        • Portal UIThe Portal User Interface (UI) is a browser user interface which provides interaction with portal using web browser based controls.
        • Referral ExchangeThis is the web service interface that has is used to interface between our referral gateways and recipient systems. It is an asymetric interface (one way) for exchanging messages with a set of metadata that declares the message type so that the recipient can validate. It is closely modelled on messageExchange. The key difference is that referralExchange will return a response id and timestamp from the recipient system.
    • MiddlewareMiddleware is software that serves to connect separate services or application components together.
      • IntegrationIntegration involves the joining of sub systems and components into a single system.
        • Network IntegrationNetwork Integration involves the joining of customer networks to facilitate information exchange.
        • System IntegrationSystem Integration is the joining of customer systems with business services.
        • Message IntegrationMessage Integration allows messaging interaction with customer messaging systems.
        • Vendor IntegrationVendor Integration allows vendor systems to be integrated with business services.
        • Data Feed IntegrationData Feed Integration is the merging of structured data feeds into a single feed for ingestion by customer systems.
      • Business ServicesBusiness Services are software-based services provided to customers, where individual services leverage capabilities from multiple backend systems and services.
        • SmartFormsSmartForms provides a customised form for entry and submission of data to a receiving system, including integration with Third Party services.
        • Secure MessagingSecure Messaging allows secure sending and receiving of patient health information.
        • On-boarding / RegistrationOn-boarding allows the addition of a new customer, it provides creation of biography information and access to customer information and provisioning of business services for that customer.
        • PortalPortal provides a web based portal for users.
        • Provider DirectoryProvider Directory allows access to all provider and organisation messaging address information by user applications.

Service Architecture 50 concepts

By @roger