Skip to content
UnifyEMPI

Quick start

The local Compose stack is the fastest way to explore the full platform. It starts three independently scalable hosts:

  • UnifyEmpi.Api for FHIR R4, SMART discovery and reviewer APIs;
  • UnifyEmpi.Portal for operational search, review and policy workflows; and
  • UnifyEmpi.Hl7v2.Host for ADT ingestion over MLLP.

Start the stack

Section titled “Start the stack”

From the repository root:

Terminal window
docker compose up --build

When all three hosts are healthy:

Terminal window
Invoke-RestMethod http://localhost:8080/health/ready
Invoke-RestMethod http://localhost:8080/fhir/R4/metadata
Start-Process http://localhost:8081
Surface Local address
FHIR and review API http://localhost:8080
Operations portal http://localhost:8081
HL7v2 MLLP listener localhost:2575
Development tenant demo
Development source demo-source

The portal seeds six invented Patient records under WDS, Cardiff and Vale, Aneurin Bevan and Velindre sources. These form three probable-match review cases.

Understand the local boundary

Section titled “Understand the local boundary”

The local stack disables authentication and gives each host its own ephemeral in-memory provider. Data disappears when a host stops, and records sent to the API or MLLP host are not visible in the portal. This is a local development environment, not a production topology.

Build and test the source

Section titled “Build and test the source”
Terminal window
dotnet restore UnifyEMPI.slnx --locked-mode
dotnet format UnifyEMPI.slnx --no-restore --verify-no-changes
dotnet build UnifyEMPI.slnx -c Release --no-restore
dotnet test UnifyEMPI.slnx -c Release --no-build

Stop the local containers with:

Terminal window
docker compose down

Next steps

Section titled “Next steps”