Atticus supports clinicians and other healthcare professionals (the end-users) with structured and standardized reporting. By reporting in a structured way they can automate plenty of tedious administrative tasks like completing registries, filling in studies, and calculating quality measures. In order to do this end-users can assemble their personal report templates using our content library. The library makes sure not everybody is reinventing the wheel.
This diagram illustrates how this all comes together
The default option to get started with Atticus is a cloud deployment. Tiro.health makes use of GDPR safe data-centers from Google which are located on Belgian territory.
At the request of the hospital or other organizations, it is possible to deploy the backend of Atticus on private servers. However, it is important that the hospital has the right infrastructure and skills to maintain the backend-service.
On-Premise deployment of Atticus
→ Identification of end-users in Atticus.
→ Passing context information such as patient identifier and encounter number to Atticus
→ Passing basic demographics of the current patient to Atticus.
→ Populate fields in Atticus with data available in other systems like LIS, PACS, RIS, … using their FHIR API.
Export and write-back reports in other formats (PDF, plain text, FHIR Document)
→ Retrieve PDF, plain text, or other formatted exports of a report created in Atticus.
Transform and complete registries and studies
→ Complete registries and studies supported by Atticus.
Transform to fill a data warehouse
→ Fill your OMOP CDM/FHIR data warehouse with structured clinical data from Atticus
Supported EHR integrations: