nuts-knooppunt

Implementation of the Nuts Knooppunt specifications.

Endpoints

• 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:
    • POST http://localhost:8081/nvi/DocumentReference/_search
    • GET http://localhost:8081/nvi/DocumentReference

Go toolchain

It's a typical Go application, so:

go test ./...

and:

go build .
./nuts-knoopppunt

Development stack

For 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:

• HAPI server, multi-tenancy enabled, using UUIDs, running on port 8080
• PostgreSQL database, for the HAPI server

Start the stack with:

docker compose up --build

Configuration

The application supports configuration through YAML files and environment variables. See docs/CONFIGURATION.md for detailed configuration options.

Quick start:

# Configuration is automatically read from config/knooppunt.yml and config/nuts.yml
./nuts-knooppunt

# Using environment variables to override config
export KNPT_NUTS_ENABLED=false
export KNPT_MCSDADMIN_FHIRBASEURL=http://localhost:8080/fhir
./nuts-knooppunt

Legacy Configuration

• KNPT_CONFIGDIR: Directory where the configuration files are stored. Defaults to ./config.

Components

This section lists the components of the application, commonly used endpoints and configuration options.

Nuts node

The embedded Nuts node can be configured through environment variables prefixed with NUTS_, or by using a configuration file called config/nuts.yml.

Endpoints:

• Public status page: http://localhost:8080/nuts/status
• Internal diagnostics page: http://localhost:8081/nuts/status/diagnostics