Patient app
- Book or reschedule an appointment
- Register at the door, get the queue number on the phone
- See lab and radiology results once released
- Visit history and outstanding bills
Software for Indonesian hospitals
Hospital information systems that match how your wards actually run.
InovasiDev builds the web SIMRS, the patient app, the staff app, and the BPJS bridges that connect them. One vendor for the system the whole hospital depends on.
- Runs on
- Browser on your existing PCs, no client install
- Bridges
- BPJS VClaim and Antrean
- Built by
- PT Inovasi Jaya Akselera
| Queue | MR no. | Clinic | Patient | Coverage | Status |
|---|---|---|---|---|---|
| A-012 | 00-14-8821 | Internal medicine | Patient A | BPJS | Called |
| A-013 | 00-09-3347 | Pediatrics | Patient B | BPJS | Waiting |
| A-014 | 00-21-1078 | Cardiology | Patient C | Private | Waiting |
| A-015 | 00-07-5510 | Internal medicine | Patient D | Insurance | Recheck |
| A-016 | 00-33-9042 | Dental | Patient E | Private | Waiting |
registrasi / 08:14
VClaim verified at check-in
Product 01
Web SIMRS
Registration, outpatient, inpatient, pharmacy, billing and reports in one browser-based system. Staff log in from any PC on the network, and every action lands in the same record.
-
Registration and queue
Issue a queue number, verify BPJS eligibility, and send the patient to the right clinic before they sit down.
-
Outpatient and inpatient
Clinical notes, diagnoses, and ward moves share the patient's medical record number, so a transfer does not fork the history.
-
Pharmacy and stock
Prescriptions arrive at the pharmacy counter as an order. Dispense against stock, and see what needs reordering.
-
Billing and claims
Charge capture from visits, ward days, and dispensed drugs, with export prepared for BPJS claim submission.
-
Reports
Daily census, revenue by unit, and visit counts, ready for the monthly review instead of built by hand in a spreadsheet.
-
Roles and audit
Access is set by role. Every record change keeps who changed it and when.
Product 02 and 03
Two apps, one record.
The patient app handles the queue and the paperwork so the front desk does not. The staff app puts the ward list and the prescriptions in a doctor's hand during rounds. Both read the same database as the SIMRS, so nothing is re-typed later.
Staff app
- Ward list for the current shift
- Prescribe and see what pharmacy received
- Approve requests without going back to a desk
- Push when a critical result lands
Your queue
A-013
Pediatrics, room 3
Now servingA-012
Estimated wait6 min
Sample data
Ward round
- 02-APatient FRx
- 02-BPatient GStable
- 02-CPatient HLab
- 03-APatient IStable
Unread results1
Sample data
What the system carries
One patient, from the front door to the discharge letter.
Each step below writes to the same record, so the billing office and the ward never disagree about what happened.
-
01
Patient app, registration desk
Arrive
Register at the desk or from the patient app. Eligibility checked against BPJS before the patient is sent to a clinic.
-
02
SIMRS queue, staff app
Wait, then consult
Queue number issued to the phone. The doctor opens the record with the visit history already loaded.
-
03
SIMRS orders, staff app
Order tests, receive results
Lab and radiology requests leave as orders. Results return to the consulting doctor, and critical ones push to the staff app.
-
04
SIMRS pharmacy
Dispense
Prescription arrives at pharmacy as an order against live stock. Dispensing updates the bill line at the same moment.
-
05
SIMRS inpatient, staff app
Admit if needed
Bed assigned from the inpatient map. Ward, nursing, and pharmacy all see the same bed and the same coverage.
-
06
SIMRS billing, VClaim bridge
Bill and claim
Charges gather as the visit happens. The claim file is ready for BPJS VClaim submission without a separate reconciliation pass.
Integration
Built to talk to the systems you already answer to.
Bridges we build
- VClaimEligibility checks and claim submission to BPJS Kesehatan.
- AntreanQueue bridging so the national appointment service and your front desk agree.
Something your hospital already runs
Labs, radiology systems, and accreditation reporting often arrive with their own API or file format. We read it and connect it, rather than asking the ward to keep two systems in step by hand.
Describe your stack in an emailCustom development
When the workflow is the hospital's own, we build the module around it.
Some units do not fit a standard module: a specialist clinic with its own intake form, a lab with a fixed report format, a programme that reports to a ministry template. We scope that with your team, build it into the same SIMRS, and keep it under the same login and audit trail.
Send the workflow you need builtWhat we ask first
- The form your staff fill in today, on paper or in a spreadsheet
- Who reads the output, and in what format
- Which existing SIMRS screens it has to link back to
Bring those three answers and the first meeting is a scoping session, not a sales call.
Tell us the hospital and what breaks today.
A short email with your bed count, the clinics you run, and the two or three tasks your staff still do by hand is enough to start. We reply with what we would ship and in what order.