Journl Streamed
Talk to an expertWebsite
  • Introduction
  • Getting Started
    • Sandbox Access
    • On-Premise
    • Cloud
  • Overview
    • Why Journl Streamed?
    • Licensing & Support
    • Features
    • Solution Architecture and Usage
  • API
    • FHIR API
      • Accessing FHIR Data
      • CRUD
        • Create
        • Read
        • Update
          • Versioned Update
        • Patch
        • Delete
          • Versioned Delete
    • Batch Upsert
  • Services
    • Security & Access Control
    • FHIR Modeling, Profiles, and Standards
    • Careplan Creation
    • Analysis on Demand
      • Standard Process
      • Types of Analysis
    • Custom Resources
    • Monitoring & Maintenance
  • Storage
    • Database
      • Database schema
    • Backup and Restore
    • Indexes
  • Integrations
    • Data Ingestion and Decoupling
    • Subscriptions and Event Notifications
    • BI & Analytical tools
      • Power BI
      • Tableau
      • Jupyter Notebook
Powered by GitBook
On this page
  1. Storage
  2. Database

Database schema

Journl Streamed’s database schema is designed to support the diverse needs of healthcare data management. It includes tables for various FHIR resources, indexed to optimize search and retrieval operations.

Resource Tables

  • Each FHIR resource type (e.g., Patient, Observation, Medication) has its own table, with columns corresponding to the attributes defined by the FHIR standard.

  • Foreign key relationships are used to link related resources, ensuring data integrity and consistency.

Audit Tables

  • To support robust audit and compliance requirements, Journl Streamed maintains audit tables that log changes to FHIR resources.

  • These tables capture details such as the type of operation (create, update, delete), the user or system initiating the change, and timestamps.

PreviousDatabaseNextBackup and Restore

Last updated 11 months ago