Skip to content
Pensieve

Procedure

Installing the bridge

Walks through installing the orophin bridge on a site, setting it up and confirming it reaches the systems it will connect.

This page installs the bridge on a site. You place one program on a machine, register it, start it, and confirm it reaches the systems it will connect.

Before you start

Done.The site exists in the hospital model.
Done.You hold the interop administrator permission.
Outstanding.A machine on the site network reaches the laboratory, information and imaging systems.
Outstanding.That machine can open an outbound connection to Pensieve.

The bridge, orophin, is one self-contained binary. It leaves a small footprint on the machine you choose.

  • pensieve-orophin
    • orophinthe bridge binary
    • keystorethe agent identity and its private key
    • outbox.dbthe durable queue of messages waiting to cross
    • configlistener ports and the drop folder

Install it

  1. 1

    Choose the machine

    Pick a server or workstation on the same network as the systems it will connect. The bridge runs on Windows and on Linux, and it binds its listeners to that local network.

  2. 2

    Download the binary

    Take the build for that machine's operating system. Place it in a protected folder, where the bridge keeps its keystore and its outbox.

  3. 3

    Register the agent

    Open Westron and register a bridge agent for the site. The console resolves the site for you and mints the agent an identity.

    A short-lived token is shown once, here. Copy it now and hold it safely.

  4. 4

    Enrol the identity

    On first start the bridge generates its own key on the machine and asks Pensieve to sign a certificate. Pensieve signs it only when the requested name matches the registered agent, and the private key stays on the machine.

  5. 5

    Point it at its listeners

    Set the port the HL7 listener binds to on the network, 2575 by default. Set the folder the bridge watches for CSV drops. Both come from the config.

  6. 6

    Start it as a service

    Run the bridge unprivileged. It opens one outbound connection to Pensieve and completes the handshake.

site server
$ orophin start
agent registered
identity enrolled
outbound channel open
listeners bound: hl7 2575, csv drop watched
status healthy

The token is shown once

The agent token appears once, at registration. Copy it then and store it safely. On the machine it is held in the operating system keystore and read only at the handshake, so the record of who the agent is stays attributable.

Confirm it reaches its systems

  1. 1

    Confirm it reaches Pensieve

    In the console, check the agent reads healthy. That verdict comes from the bridge's own heartbeat, so a quiet moment reads differently from a dropped bridge.

  2. 2

    Confirm each system

    Send a test message from each system, or run the connection test from the console. Check that each connection reads healthy and carries a recent successful call.

Register a bridge agent
Site
Agent name
Register
Token, shown once
Registering an agent mints its identity and shows its token once. The bridge enrols against that identity on first start.

Common questions

Where does the bridge run?

On one machine on the site network, alongside the systems it connects. One agent serves one site.

Do I type the site into the bridge?

The console resolves the site off the registered agent, so the bridge carries its identity and the platform resolves the rest.

Define a connection and hold its credentials in connections and credentials.