architecture and technological solutions

Business Architecture

Architected to provide interoperability of health information through the use of a set of semantic resources and clinical interoperability models - DCM - detailed clinical models already developed and ready to use in different integrations, among them: (1) Clinical Care Record (consultations); (2) High Summary; (3) Emergency Service; (4) Exam Results; (5) Immunization Summaries; (6) Patient Health Summary.

The EHRRunner® Platform provides a longitudinal Electronic Health Record (RES) service. It is an identified clinical information service, which aggregates and shares health information about individuals in a care network, providing standardized mechanisms in HL7 FHIR R4 for interoperability between different systems.

Information Architecture

EHRRunner® has a dedicated and separate treatment for information architecture, based on international digital health standards. In this way, the informational assets of the clinical domain are structured in templates OpenEHR and decomposed into HL7 FHIR R4 features capable of operating with clinical and administrative health terminology.

This architecture allows the EHRRunner® platform to adapt to different clinical and administrative cases, with consistent use of standardized services, with immediate support for other clinical use cases.

Technical architecture

The EHRRunner® Platform has 100% service-oriented architecture and implemented in cloud computing infrastructure, optionally in installations on premise. It combines native cloud services and a modern service infrastructure, consisting of an interoperability bus, API management, access control and identity management, with specialized services for MPI (Master Patient Index), CDR (Clinical Document Repository), Consent, Terminologies and Metadata. As a result, all platform features are available through HL7 FHIR R4 APIs (various features and national and international profiles), with extensions available for IHE profiles (MHD, APPC, XDS.b, PIXv3, PDQv3).

A hybrid data architecture is used, where they are considered for primary use (health professionals): 1) Indexing and Retrieval (document registry and document repository); 2) Summary; 3) Access consented (all access authorizations are logged and made available to users); 4) Anonymization (data is persisted anonymized); and 5) Clinical decision support. Already in secondary use (analytics), the data is anonymized, de-identified, enriched with data from other sources and aggregated, to be available via APIs (analytics APIs).

Send a Message
Powered by TranslatePress »