Skip to content
Pensieve

Procedure

Building an app

Walks through composing a tool in Durin by arranging building blocks over governed data, and publishing it to the people who need it.

Composing a tool in Durin takes a handful of steps. You arrange building blocks over governed data, wire the actions the tool performs, and publish it to the people who need it.

Before you start

Check these three things first. If one is missing, the build stalls at the step that needs it.

Done.You hold builder access in the console.
Done.The data your tool reads is already in the platform.
Outstanding.You know which role should hold the tool.

Compose the tool

Work down the steps in order. Each one leaves the tool in a state you can preview.

  1. 1

    Open Durin and name the tool

    In the dock, open Durin and choose New tool. Give it a name your staff recognise on sight, such as Ward round board. The name is what appears in their dock later.

  2. 2

    Choose the data it reads

    Pick the part of the ontology the tool draws on: the record, orders, charges or the hospital model. The tool reads through the same governed data every tool uses, so the figures stay in step with the rest of the platform.

  3. 3

    Arrange the building blocks

    Drag a Table, a Detail panel, a Form or a Chart onto the canvas. Arrange them the way the work reads on the ward. If a block stays empty in preview, check that your own role reads that part of the record.

  4. 4

    Wire an action

    Add an Action, such as placing an order or opening a form. Durin routes the action through the same path a shipped tool uses. If a person lacks the permission for that action, the control stays out of their reach.

  5. 5

    Preview against your own access

    Choose Preview. You see the tool exactly as your own role and relationships allow, so the preview is an honest rehearsal of one person's view.

  6. 6

    Publish to a role

    Choose Publish and pick the roles that should hold the tool. It appears in their dock at their next sign-in. If you pick the wrong role, change the roles on the tool and publish again; the dock follows.

Publishing grants the tool, not the data

A built tool inherits the platform's authorisation. Publishing it to a role hands them the tool. Each person still sees only the record their role and the patient's admission entitle them to, so a clerk and a clinician open the same tool and read different rows.

The build canvas
Blocks
Ward round board
Preview
Table
Detail panel
Publish
The build canvas, with a block palette on the left, the tool laid out in the centre, and the preview and publish controls to hand.

Make a widget

A widget is a compact panel a person pins to the desktop. To make one, choose New widget in place of New tool, then follow the same steps. Keep it to one table or one chart, so it reads at a glance. Widgets sit alongside the ones covered in desktop widgets.

Common questions

What happens if I publish to the wrong role?

Change the roles on the tool and publish again. The dock updates for each affected person at their next sign-in.

A block stays empty in preview. Why?

Preview shows you only your own permitted view. If a block is empty, your role reads none of that data. Check the block against a role that holds it.

Does a form in my tool behave like a real form?

Yes. A form block writes back through the record with the same validation and locking as any built form.

Read how a built tool inherits access.