How santeonnl/orca works
Project type and purpose
• ORCA is a full-stack, microservices-style platform implementing the Shared Care Planning FHIR specification.
• It consists of:
• A Go-based backend (“orchestrator”) that exposes internal and external FHIR APIs, implements Care Plan Contributor and optional Care Plan Service roles, handles OIDC/OAuth2, messaging, discovery, subscriptions, and acts as a proxy to EHR FHIR APIs.
• One primary Next.js frontend for care professionals.
• Two auxiliary Next.js simulators (hospital_simulator and viewer_simulator) as demo/test clients.
• Helm charts and Docker definitions for Kubernetes/Azure deployments.
File structure
• Top-level directories:
• “frontend”: Next.js application for real care professionals.
• “hospital_simulator” & “viewer_simulator”: Next.js demo apps with DashboardLayout, API routes for FHIR, delivery, bgz, and authentication flows.
• “orchestrator”: Go microservice with subpackages:
– careplancontributor (Task placement/filling, Task engine, OIDC clients)
– careplanservice (CarePlan/CareTeam management, FHIR operations, webhook)
– messaging (Azure ServiceBus, in-memory, HTTP)
– healthcheck, events, user/session, ADR, cmd entrypoints
– lib/* (coolfhir client, az key vault, crypto, otel, validation, etc.)
– util (CLI utilities)
• “deployments”: Helm charts (orca, nuts, nuts-admin, fhir) and local Docker-Compose for dev.
• “e2e-tests”: Go-based integration tests driving orchestrator and simulators.
Key points from README
• ORCA’s high-level roles:
• Frontend UI for Task negotiation and CarePlan viewing.
• Orchestrator as Care Plan Contributor and optional Care Plan Service, proxying FHIR APIs.
• Integration with local EHR FHIR API, external SCP nodes, Nuts discovery, and OAuth2/OIDC servers.
• External dependencies: Azure Key Vault, Azure Service Bus, SQL for Nuts, any FHIR R4 API.
Final advice
• Be exhaustive: break the orchestrator into its major subdomains.
• Real deployment boundaries (containers, clusters, services).