Actions
Feature #3558
openFeature #63: DigiPatho Web -- Development, Validation, Certification and Deployment
HL7 FHIR-compliant API layer
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:
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