flowrise-hms/fhir

FHIR R4 server module for FlowRise HMS

Maintainers

Package info

github.com/Flowrise-HMS/FHIR

Type:laravel-module

pkg:composer/flowrise-hms/fhir

Transparency log

Statistics

Installs: 0

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 0

Security

Advisories: 0

Aikido package health analysis

dev-main 2026-07-10 11:28 UTC

Requires

MIT 267eadcf6d7eae12ace18c9d698e8da0fbbb510a

apihl7interoperabilityhealthcarefhir

Published on Packagist.org on 2026-07-10 11:29 UTC

This package is auto-updated.

Last update: 2026-07-10 11:29:09 UTC

README

In one sentence: The FHIR module exposes a FHIR R4 REST API for national and third-party health data exchange.

Current status

In progress. Infrastructure (validation, search, pagination, capability statement) is built. Multiple resource types are registered. SMART on FHIR, bulk export, and remaining clinical/financial resources remain planned.

See Module Status for the canonical rollout matrix.

What is implemented

  • API base: /api/v1/fhir/{resource} (Sanctum-authenticated)
  • Metadata: GET /api/v1/fhir/metadata (capability statement)
  • Full CRUD: Patient (Patient module transformer), Practitioner and PractitionerRole (Staff module transformers)
  • Read/search: Organization, Location, HealthcareService (Core transformers); Encounter, Condition, AllergyIntolerance (Clinical); Observation (Diagnostics); Appointment, AppointmentResponse (Appointment); InventoryItem (Inventory)
  • Infrastructure: FhirResourceRegistrar, FhirValidator, search parameter handling, content negotiation

What is deferred

  • Additional FHIR resources (DiagnosticReport, Claim, Coverage, ServiceRequest, Medication*, Schedule, Slot, etc.)
  • Full CRUD for resources currently exposed as read/search only
  • SMART on FHIR authentication
  • Bulk data export ($export)
  • CCD document generation

Dependencies

  • Registers transformers from domain modules (Patient, Staff, Core, Clinical, Diagnostics, Appointment, Inventory) when those modules are enabled
  • Does not require every clinical module at runtime; registrations use class_exists guards where appropriate

For developers

  • Namespace: Modules\FHIR\...
  • Service provider: Modules\FHIR\Providers\FhirServiceProvider
  • Routes: Modules/FHIR/routes/api.php
  • Tests: Modules/FHIR/tests/ (capability, appointment integration, infrastructure unit tests); domain modules include transformer unit tests