Project

General

Profile

Actions

Feature #3558

open

Feature #63: DigiPatho Web -- Development, Validation, Certification and Deployment

HL7 FHIR-compliant API layer

Added by Thara S Pillai over 1 year ago. Updated 8 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Start date:
05/05/2025
Due date:
12/22/2025 (about 8 months late)
% Done:

0%

Estimated time:
(Total: 0:00 h)
Planned Due Date:

Subtasks 5 (5 open0 closed)

Activity #3559: Explore on HAPI FHIR java libraryNewSneha K V05/05/2025

Actions
Activity #3560: Integrate HAPI FHIR libraryNewSneha K V05/05/2025

Actions
Activity #3561: Identify the end points to publish NewAswathy M G05/05/2025

Actions
Activity #3563: Develop for API end pointsNewAswathy M G05/05/2025

Actions
Activity #4488: Setup HAPI FHIR server – JPA Server (R4) + PostgreSQLNewAswathy M G12/22/202512/22/2025

Actions
Actions #1

Updated by Thara S Pillai over 1 year ago

  • Subtask #3559 added
Actions #2

Updated by Thara S Pillai over 1 year ago

  • Subtask #3560 added
Actions #3

Updated by Thara S Pillai over 1 year ago

  • Subtask #3561 added
Actions #4

Updated by Thara S Pillai over 1 year ago

  • Subtask #3562 added
Actions #5

Updated by Thara S Pillai over 1 year ago

  • Subtask #3563 added
Actions #6

Updated by Thara S Pillai 8 months ago

  • Subtask deleted (#3562)
Actions #7

Updated by Thara S Pillai 8 months ago

  • Subtask #4488 added
Actions #8

Updated by Thara S Pillai 8 months ago

  • Implement an ABDM-compliant FHIR R4 server.
  • Make integration APIs FHIR-compliant
  • Add a FHIR mapping/adapter layer
  • Deploy an in-house FHIR server
  • Store diagnostic reports and observations in FHIR
  • Keep slides and AI artifacts externally referenced
  • Follow ABDM implementation guides. Enforce ABDM consent and audit rigorously
  • Digital Pathology HIP exposing PDF reports and AI-derived observations
  • Wrap PDFs inside FHIR
  • Structure AI outputs as Observations, not embed them invisibly in PDFs
  • Setup HAPI FHIR – JPA Server (R4) + PostgreSQL (https://hapifhir.io/hapi-fhir/docs/server_jpa/get_started.html)
  • using Docker on Windows
  • FHIR server uses PostgreSQL to store clinical metadata
  • pathology application creates FHIR resources and sends them to the FHIR server. PDF is referenced, not stored, in the FHIR database
  • FHIR server provides APIs to store and retrieve these resources
  • HIU → ABDM Gateway → HIP Integration Layer → FHIR Server
Actions

Also available in: Atom PDF