Every feature, in detail.

Create, update, and monitor patient cases with a complete activity feed. Each case carries a status code — Awaiting Surgery, Post-Op, Awaiting Results, Discharged — visible as a coloured chip on every list item, so a glance tells you where the patient is in their pathway. Every status change, every assignment, every medical-contact decision is logged with author, timestamp, and the before/after value — so the whole committee shares the same picture, and audit questions answer themselves.

Every case has a designated primary and an optional secondary contact. Both see the case in real time, both receive notifications on changes, and reassignment is one tap. The model is deliberately simple — it mirrors how most HLCs already split a case between a lead and a backup.

Each HLC has a unique shareable URL on hlccasemanager.org/register. The Chairman or Secretary copies it from Settings and passes it to congregation elders, who use it to submit a patient referral directly into the committee's queue — patient details, hospital, urgency. The submission contains the same fields a member would enter in the intake screen, and the case is immediately visible to every assigned member.

Before any new case can be created, the member must confirm that the patient has given explicit consent to process their health data under GDPR Article 9(2)(a). The confirmation is recorded with the patient's name, the member who captured it, and the timestamp — alongside a one-tap link to the privacy policy. The app simply refuses to create a case without that affirmation.

Record the doctors, surgeons, and specialists you work with. Track specialty, hospital, cooperative status, and HLC-31 consent. Set follow-up reminders per case. The same contact can be linked across cases, so a consultant you spoke to in March is still one tap away in September.

Meetings, training, presentations, outreach calls — all in one place. Month, week, list, and statistics views. Assign attendees, link an event to a case for context, and let the app handle attendee reminders via push notification.

Each case can record the patient's pre-existing conditions from a curated, multilingual catalog. The list is encrypted at the field level like the rest of patient data, and helps the primary contact prepare the conversation with each consultant on the doctor team — anaemia, ongoing anticoagulant therapy, comorbidities, and the rest.

Closing a case is a guided wizard, not a single button. The member writes a one-line closure summary, makes a per-contact follow-up decision (who calls back, when), and confirms the discharge. As soon as discharge is confirmed, the patient's identifying information is permanently anonymised — the operational record is kept for the committee's learning, but nobody can tell whose case it was.

Every hospital the committee works with is a first-class record in its own directory — address, specialties offered, last-verified date, and which cooperative doctors work there. Useful when planning a presentation, choosing where to send the next member for training, or simply confirming who you've already established at hospital X.

New case assigned to you, status changed on a case you back up, a medical contact added, a follow-up due, a new event scheduled — every committee-relevant change can reach the right people without a group chat. Notifications respect quiet hours and can be silenced per category.

A local SQLite database keeps every case readable when you're underground or on a hospital floor with no signal. Edits made offline are blocked rather than queued — so nothing is silently lost and you never end up resolving a conflict with yourself an hour later.

Members enable Face ID or Touch ID in Settings. From then on, the app authenticates them on launch and re-authenticates the moment the phone locks or the app is backgrounded. The iOS app-switcher preview is automatically blurred, so a glance at the phone in a hospital corridor never reveals a patient name.

Patient data, case timeline updates, push-notification content, HLC member personal data (name, email, mobile, avatar), patient medical conditions, and audit-log entries are encrypted at the field level with AES-256-GCM before they leave the device. Each committee holds its own key — the backend stores ciphertext only. Even an attacker with full database access cannot read your data.

Three roles: Chairman, Secretary, and Member. Chairman and Secretary add, suspend, and delete members and reassign roles. Sensitive operations (deleting a contact, archiving a closed case) require Chairman or Secretary. Members can do everything else. Members sign in with a @jw-hlc.org email — country-specific suffixes such as @jw-hlc.org.uk, @jw-hlc.org.fr, or @jw-hlc.org.es are also accepted.

Separate from the per-case timeline, a server-side audit log records the small set of admin events that need permanent attribution: Chairman or Secretary role transfers, Assistant assignments and revocations, and the anonymised summary written when a closed case passes its retention date. Read access is scoped to Chairman and Secretary of the HLC concerned. The day-to-day record of who changed what on a case lives on the case itself — see Real-time case tracking.

The app runs on phones, iPads, and Android tablets — and on each of your devices simultaneously, with changes syncing across them in real time. On tablets in landscape, the sidebar stays visible, content is capped at a comfortable reading width, and the case-detail screens use a two-column layout instead of stacked cards.

The interface is fully translated into English, French, and Spanish. The architecture is single-file: a new language requires one translation file and no code changes. Write to us if your committee needs another language.