Skip to main content

View FHIR resources

Use Case

Review and export actual data without distorting layers or blindness to uncovered subsets.

According to the Hospital Future Act (KHGZ) in Germany or 21st Century Cures Act in the US medical data in a hospital must be stored in an interoperable way which can be achieved by the means of a FHIR®-based data integration server. A data integration server in a hospital is supposed to store a variety of data, depending on the specific needs and orientation of the hospital such as electronic health records (EHR), finanical data, administrative data, clinical data or research data. In addition to other data sources, the data integration server retrieves manually documented or device-generated data from the hospital information system (HIS) as well as information from various systems and devices such as the laboratory.

Ideally, a hospital information system would be able to present the medical data in its completeness regardless of the source. Unfortunately, that is not the case. Most hospital information systems are based on a proprietary architecture, are not yet speaking FHIR® natively. Singular specialized systems only enable the access to a particular subset of the medical records. Even if a system would speak FHIR® natievely, it will be propably blind to data that is not a hardwired into its frontend.

Records solves this problem by listing the actual FHIR® resources without distorting layers and making the contents of individual resources generically readable.

Additionally, software solutions that are not natively supporting FHIR® are not writing directly to a data integration server. Instead they store data in a proprietary format that needs transformation and is occasionally pushed to a FHIR® server. This transformation process is prone to errors. The results need to be checked for completeness and validity on an ongoing basis, especially when new profile requirements are introduced. The data on the DIS is hard to view and to validate in order to check the results. FHIR® experts have to read it in JSON format and retrieve profile errors and warnings via command line. Records on the other hand enables for a quick review of the transformation results including precise assessment of validity. Conclusions about what has to be fixed in the source software e.g. mapping or the ETL route, can be made and validated more quickly.

FHIR® data is occasionally reviewed and exported for analysis at various points in the healthcare process, depending on the specific needs and goals of the review such as clinical review, quality improvement, research or population health management. Records enables to browse the complete FHIR® datasets within the scope of the authoriation, view the actual resources and export it in various formats.

    Check out Records

    Explore & edit medical records with ease.

    About Records