Implementation of the Nuts Knooppunt specifications.
A demonstration Electronic Health Record (EHR) application showcasing Dutch healthcare data exchange use cases including BGZ exchange and eOverdracht workflows.
See mock-components/demo-ehr/README.md for detailed documentation and setup instructions.
- Health check endpoint: http://localhost:8081/status
- mCSD Admin Application: http://localhost:8080/mcsdadmin
- mCSD Update Client force update: POST http://localhost:8081/mcsd/update
- NVI FHIR gateway endpoints:
- Registration endpoint: POST http://localhost:8081/nvi/DocumentReference
- Search endpoint:
- Demo EHR Application: http://localhost:3000
See docs/CONFIGURATION.md for configuration options and instructions.
See docs/DEPLOYMENT.md for how to deploy the Knooppunt in your XIS/healthcare system.
See docs/INTEGRATION.md for how to integrate the Knooppunt in your local XIS/healthcare system.
See docs/ARCHITECTURE.md for an overview of the architecture and design of the Knooppunt (for Knooppunt developers).
It's a typical Go application, so:
go test ./...and:
go build .
./nuts-knoopppuntFor a complete overview of the deployment options, see docs/DEPLOYMENT.md.
A docker compose config is provided to run a set of services that are useful for development:
- Knooppunt - Main application running on ports 8080 (API) and 8081 (internal)
- HAPI FHIR Server - Multi-tenant FHIR R4 server with NVI support, running on port 7050
- Aspire Dashboard - Observability dashboard for traces, logs, and metrics on port 18888
- Demo EHR - Demo application (optional, use
--profile demoehr) - PEP (Policy Enforcement Point) - NGINX-based reference implementation (optional, use
--profile pep)
Start the base stack with:
docker compose up --buildStart with demo-ehr:
docker compose --profile demoehr up --build