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

Database

PreviousMonitoring & MaintenanceNextDatabase schema

Last updated 9 months ago

Journl Streamed employs a robust and flexible storage architecture using open-source to manage both raw data and FHIR-structured data efficiently. This ensures high performance, scalability, and reliability, which are crucial for handling healthcare information.

Key Components

Primary Database

  • The primary database is responsible for storing FHIR resources. It is optimized for fast read and write operations, ensuring quick access to healthcare data.

  • Journl Streamed uses a combination of relational and NoSQL databases to balance complex querying capabilities with scalability needs.

Raw Data Repository

  • Raw data, such as HL7 messages, CSV files, or other formats, is stored in a dedicated repository before being mapped to FHIR resources.

  • This repository supports various data formats and acts as a staging area for data transformation processes.

Transformation Layer

  • The transformation layer is responsible for mapping raw data to FHIR resources. It ensures that data is converted accurately and consistently, adhering to FHIR standards.

  • This layer includes validation mechanisms to ensure the integrity and quality of the transformed data.

PostgreSQL