In development
The road to your iPhone.
From the app foundation to a tested prototype, then a small practice pilot. Here is the delivery sequence. Release dates will follow testing and review.
Read this first
clinicomm is demonstration and development work. It is not released, it is not on any app store, and no clinic is using it. Nothing on this page is a commitment to ship a named feature on a named day; it is the sequence we are working in, and the sequence is the part we are confident about.
NowThe local foundation
- The parts that run on a laptop The app foundation and conversation screens are in local development, using synthetic examples. They are not yet connected to a live messaging service.
- Product discovery with real practices Conversations with practice staff about how coordination actually happens today, what fails, and what has already been tried. This runs alongside the code rather than after it, and it is why the feature list is short.
- Clear product boundaries Staff communication is the focus. The first release is not intended for emergency paging, diagnosis or medication orders.
NextMaking it a working system
- Authentication Sign-in for practice staff, with a second factor required rather than offered. Nothing else on this list is meaningful until an account is a real thing.
- The messaging service The request paths that send a message, read a thread, and let a device that has been offline catch up. This is the piece that turns a design into software.
- A prototype on a physical iPhone The app running on a handset in a pocket, talking to a real service, rather than in a simulator against a stub. That is a demonstration prototype and we will keep calling it one.
Before any pilotThe work that gates a real clinic
- Operational review The written procedures a practice's administrator would expect a vendor to have, reviewed and in force — how access is granted and removed, what happens when a device is lost, who is called at two in the morning, and how an incident is handled.
- Independent testing Testing by people who did not build it, with the findings worked through rather than filed. Our own test suite is evidence about our own assumptions and is not a substitute for this.
- The written agreements The contracts that have to be in place between a practice and a vendor, reviewed by counsel, before either party puts a name on anything.
- The infrastructure it will actually run on A cloud account dedicated to this product alone, separate from every other project this company runs, provisioned deliberately with its spending watched from the first day.
LaterPilot, then the platforms that follow
- A small pilot through TestFlight A limited number of practices, invited individually, running the app through Apple's test distribution. Everything under Before any pilot has to be finished first, and there is no waiting list to join today.
- App Store release Public availability on iPhone, after the pilot has run long enough to have taught us something. There is no listing to link to yet.
- Android and desktop Android remains on the mobile roadmap. Windows and macOS follow the clinic beta, for staff who spend more of their day at a desk.
- What is deliberately not in version one Voice and video, patient-facing messaging, records-system integration, a browser client, and anything generative anywhere near clinical message content. Each of those is a decision we have taken, not a gap we have overlooked.
Talk to us
If this order looks wrong for your practice, say so.
The sequence above is a judgement, and judgements improve when somebody who runs a clinic argues with them. We would rather hear that now than after it is built.