# Healthcare App: Software that bends to the hospital

> An internal hospital operations application, configurable to each hospital's SOP and integrated with JKN and SATUSEHAT.

- Site: Falah Isnan (https://falah-isnan.com/work/healthcare-app)
- Author: Falah Isnan (https://falah-isnan.com/)
- Published: 2026-09-23
- Updated: 2026-09-23
- Discipline: Operations software
- Focus: Local flexibility, external exactness
- Year: Not recorded
- Role: Hospital operations application
- Client: Private company
- Stack: Not published
- Access: Private project

Draft — role and outcomes to be confirmed.

## The problem

Every hospital runs its own procedure, and none of them will change it for a piece of software. The national systems the hospital reports into will not change either.

## The approach

Make the route through the application configuration rather than code, keep the operational record fixed underneath it, and build the JKN and SATUSEHAT integration against their requirements.

An internal application supporting hospital operations — the working day of a hospital rather than one department's tooling.

It also has to agree with the national systems it reports into, which makes correctness a requirement from outside the building as well as inside it.

## What the project is

### Every hospital runs its own SOP.

Two hospitals doing the same clinical work will not do it in the same order, with the same roles, or with the same checks. The SOP is local, and it is not up for negotiation with a piece of software.

So the flow in the application has to be adjustable to the hospital using it, rather than the hospital being adjusted to the flow.

### The flow bends. The record does not.

Registration, service, and the record that comes out of it are the operational line the software follows. What varies is the route through it, not the fact that it has to be complete at the end.

Flexibility that loses the record is not flexibility. The branching has to sit above a structure that stays fixed underneath.

### JKN and SATUSEHAT are not optional.

The project includes integration with government systems, including JKN and SATUSEHAT. Those interfaces define their own expectations, and the hospital's SOP does not get to change them.

That pins one end of the system: however local the flow gets, what leaves it has to be something the national systems will accept.

## The hard part: A flow that fits somebody else's SOP

The application has to be configurable at the hospital's end and exact at the government's end, at the same time.

1. **Let the hospital's SOP choose the route.** The order of steps, who performs them, and which checks apply are configuration rather than code. A hospital adopting the system describes its own procedure instead of adopting one.
2. **Keep the operational line intact.** Registration, service, and record stay the spine of every route. However the branching goes, the same information has to exist by the end of it.
3. **Meet JKN and SATUSEHAT on their terms.** What the national systems require is fixed and external. The integration is built against their expectations, so local flexibility never becomes a reporting failure.

## What you can open

Internal tool. The application, its link, and the client hospital's name are not published. The year of the engagement is still to be confirmed before this page is treated as final.