Clinic management system and electronic medical record

A clinic system built in Hebrew, from the ground up

CareOS runs your calendar, patient chart, visits, prescriptions, lab work, billing, and patient portal in one system. Writing direction, the local calendar, the shekel, and the national ID are part of the product's foundation, not a translation layer pasted on top.

Request a demo Open the live demo

The demo runs in your browser. No installation, no commitment.

The flow board: who is in the clinic right now, in which room, and the actual wait time.
A clinic management and electronic medical record (EMR) system for private clinics in Israel.
FHIR R4 — standard resource interface HL7 v2 — lab result intake C-CDA — summary import and export SMART on FHIR and OAuth2 — app authorization DICOM and PACS — imaging studies Object storage for files and video SMS — reminders and messages Email — documents and alerts

Three problems that recur in almost every clinic

These aren't matters of taste. They are failures that create duplicate work, and sometimes clinical error.

1

Software that fights the language

An interface translated after the fact produces mixed lines where numbers, units, and comparison signs appear in reversed order. In a table of lab values or blood pressure, that isn't a cosmetic issue — it's wrong data in front of the physician's eyes.

2

Work that lives outside the record

Photos on the practitioner's phone, treatment videos on an external drive, imaging in a separate system, consents on paper. When information sits outside the chart, you can't find it in time, and you can't prove who viewed it.

3

Every small change means calling the vendor

Adding a field to an intake form, reordering demographic fields, or granting a new permission to a role — each one turns into a support ticket, a quote, and a wait. A clinic changes its processes faster than a vendor can code them.

The system

What's in the system

Ten areas that work on the same patient chart and the same calendar, with no export and import between them.

Calendar and appointments

Day, week, and month views per practitioner, room scheduling, appointment types and statuses, a waitlist, follow-up recalls, and a live flow board that shows who has arrived, in which room, and how long they've been waiting.

The patient chart

Demographics in a configurable screen layout, a problem list, allergies with reaction and severity, medications, history, documents, and a financial ledger.

Visits and forms

Visit summaries, clinical forms such as vital signs, SOAP, and review of systems, an electronic signature that locks the visit, and permissions at the level of the individual form.

Prescriptions

Write a prescription from within the visit, checked against the allergies recorded in the patient chart before it is saved.

Orders and results

Lab orders, result intake in the HL7 standard, flagging of out-of-range values, a review-and-sign-off workflow by the practitioner, and trend graphs over time.

Billing and collections

A charge page with diagnostic justification, claims, payment posting, a patient ledger, eligibility checks, and financial reports.

Patient portal

Patients see appointments, results, and documents, complete questionnaires in advance, message on a secure channel, and pay online.

Treatment recording

Start and stop a recording tied to a specific visit, with a documented consent gate, bookmarking of key moments, and a full access log of everyone who viewed the material.

Media and imaging

A single media tab per patient that shows images, video, PDF files, and DICOM imaging studies together, regardless of where each file is stored, opening the right viewer for each type.

Administration and permissions

492 configuration settings, a permission matrix of 65 access objects across 6 roles, a form designer for changing layouts without a programmer, value lists, and an audit log with an integrity signature on every row.

See what the CareOS system includes

How it actually looks

Six screens from the prototype. Every screen is fully in Hebrew, right to left.

The flow board: who is in the clinic right now, in which room, and the actual wait time. The patient chart: problems, allergies, and medications at a glance, with a configurable layout. An open visit with a vital-signs form, before the signature that locks it. Lab results with out-of-range values flagged and a trend graph over time. The media tab: images, video, and imaging studies for the same patient in one place. The permission matrix: what each role may view, add, and edit.

Hebrew and RTL are a safety requirement, not styling

In bidirectional text, a number sitting inside a Hebrew sentence can be displayed in reversed order. In a medical system that isn't a display glitch — it's wrong clinical data.

Partial translation is a built-in risk

The familiar open-source alternative in this field provides RTL support that amounts to roughly 5% of its stylesheet by CSS-rule count, and a Hebrew interface translated at about 61% by string count. The meaning of those numbers is mixed screens: part Hebrew, part English, and part aligned to the wrong side.

Blood pressure that flips

The value 140.4 / 87.6 can be drawn on screen as 87.6 / 140.4 — systolic and diastolic swapped, and the unit jumping ahead of the number. A hypertensive reading is shown as hypotension. A screenshot won't catch it, because a reversed range still looks like a range.

A greater-than sign drawn as less-than

A lab reference range written as >60 is drawn inside a Hebrew paragraph as 60<. The character doesn't move — it is rendered as its own mirror image. A result that is within range reads as abnormal, and vice versa. The same mechanism turns a credit into a charge.

The fix is in the infrastructure, not the screen

In CareOS, every compound value — a range, a ratio, a signed amount, a date and time, a dose with a unit — passes through a typographic formatting layer that isolates it as a single unit. Automated tests verify the actual character order, not just how the screen looks.

The numbers behind the product

48
screens in the clickable prototype
492
configuration settings in the admin screens
65
permission objects across 6 roles
21
specification chapters written before the first line of code

Interfaces and standards

The system speaks in accepted standards, so your information doesn't get stuck in one place.

FHIR R4 — standard resource interface HL7 v2 — lab result intake C-CDA — summary import and export SMART on FHIR and OAuth2 — app authorization DICOM and PACS — imaging studies Object storage for files and video SMS — reminders and messages Email — documents and alerts

The blog

Practical articles on clinic management, clinical documentation, privacy, and switching between systems. No empty jargon, and with conclusions you can apply next week.

Blog

Want to see this running on your clinic?

We'll walk through the calendar, the patient chart, and the billing flow together, and see what fits and what's missing. A half-hour conversation, no slide deck.

Schedule a demo