Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

This page has been superseded by Interacting with the Reporting Service and Reporting API .

Modelling overview - Reporting model

The reporting service is a FHIR server that provides REST endpoints for extracting ehealth data. Data is returned as a FHIR Binary resource with a content element containing the data in base64 zip compressed JSON format (application/gzip-json).

Technical reports

Technical reports is part of the Operating status report.

With access to Splunk it is possible to create report and dashboards for technical reporting.

Accounting reports

  • SSL-orders: Orders including history.

  • Measurement-stats: Statistics on Observations, QuestionnaireResponses and Media.

  • Careplan-duration-stats: Statistics on CarePlans and status changes.

  • Practitioner-stats: Statistics on Practitioners related to Organizations and CareTeams

Management reports

  • Careplan-duration-stats: Statistics on CarePlans and status changes.

  • Careplans-by-patient: EpisodeOfCare and Plan resources

  • Careplan-and-episode-of-care-stats: Statistics on the number of Careplans and EpisodeOfCare for each Plandefinition

  • Careteam-stats: Statistics on EpisodeOfCare, CarePlan and Tasks assigned to a CareTeam

  • Careplan-customization-stats: Statistics on Patient specific customizations of CarePlans

Clinical reports

Patient-total: All clinical resources for Patients

Usage reports

  • SSL-orders: Orders including history.

  • Practitioner-gdpr: All data related to a Practitioner

  • Patient-gdpr: All data related to a Patient

  • Careplans-by-patient: EpisodeÓfCare and Careplans

  • Patient-devices: Devices assigned to a Patient

Reporting REST endpoints

Each type of report has two endpoints:

  • $fetch-<reportname>

    • run report - run report synchronously and return resource with result.

  • $schedule-<reportname>

    • schedule report - schedule a report for later batch execution. The returned result is an empty placeholder that identifies the resource to be retrieved later. When the batch is run, the resource will be updated with the result. The report will be stored in the database and will be available for retrieval for a limited time period. The scheduled reports will be generated during the night, and will usually be available the next morning.

Currently the following reports are supported:

...