MedAligna
Start free trial

Changelog

What shipped, and when

A dated record of what MedAligna can do that it could not do before. Every entry names something you can go and use in the demo or the trial today: no roadmap, no previews, no backdating. The most recent release was July 16, 2026.

Is MedAligna actively developed?

That is the right question to ask a small vendor, and this page is the only answer we can give you that you do not have to take on faith.

The thing you should worry about with a company our size is not whether the software is good; you can check that yourself in the demo, in about four minutes, without giving us an email address. It is whether we will still be here next year, because the schedule is the thing that keeps the floor staffed and a vendor who vanishes takes it with them. Nobody can prove a future. What we can do is make the past checkable.

So this page is deliberately disprovable. Every entry below names a specific capability with a specific date, and each one can be verified from outside: open the demo and try to schedule Marisol on the Friday after her licence expires, and you are looking at the credential blocking listed under 14 July. If we ever start writing entries you cannot check, the page has become an advert and you should treat it as one.

How often does MedAligna ship?

As often as something is finished. The dates on this page are the only answer we are prepared to give, and they are the only one worth anything.

We are not going to promise you a release every Thursday. A vendor who commits to a cadence eventually ships something on a Thursday for the sake of the Thursday, and what gets shipped is whatever was small enough to finish, which is how a changelog fills up with entries nobody asked for while the thing you actually need waits behind them. The commitment we will make is the harder one: an entry appears when a capability does, and not before.

Which leaves you with a measurement rather than a promise, and a measurement you take yourself. Every release below carries the date it happened. Come back in three months and look at the gap between the newest date and today's: that number is the only honest thing anyone can tell you about a small vendor's pace, and unlike a commitment on a marketing page, we cannot edit it in our favour.

What are the rules for this page?

Four, and they are the sort that only matter when following them is inconvenient. Entries are tagged New for a capability that did not exist, Improved for one that got better, and Fixed for something that was wrong.

01Real dates, never backdated

The date on an entry is the date the thing shipped. A young product is tempting to age artificially: a few entries moved back a year, a version number that implies a history. We do not, and the reason is selfish: a fabricated date is the one lie on this site a customer could eventually catch, and catching it would make every other claim worth re-examining.

02What you can DO, not what we refactored

Nobody outside this building cares that a module was extracted. An entry has to name something a scheduler, a nurse or an administrator can now do that they could not do the week before, which is a harder bar than it sounds, and it is why some weeks of work produce no entry at all.

03Nothing listed that has not shipped

No roadmap, no previews, no 'coming soon' dressed up in the past tense. If it is on this page it is in the product right now, and you can go and find it in the demo or the trial without asking us where it is.

04The fixes stay up

The account-deletion bug below was ours, it was bad, and it is still on the page. A changelog with no 'Fixed' entries is not a product without bugs; it is a product whose changelog is marketing.

What has changed in MedAligna recently?

Most recently, on July 16, 2026: the credential wallet, federal exclusion screening, and the fill waterfall that exhausts your own staff before it suggests an agency. Before that, the rules engine and the grid everything else sits on.

REST API & outbound webhooks

  • NewA REST API on Enterprise. Read your schedule, staff, credentials, open shifts and on-call chain from anything else you run. Keys are created and revoked in the app, shown once, and stored as a hash; revoking one takes effect on the next request, with no cache to wait out.
  • NewOutbound webhooks. We POST a signed body the moment a shift is claimed, a swap is approved, or an on-call board is published or taken down: HMAC-SHA256 over the raw body, with an event id you can dedupe on. Failed deliveries retry with backoff, and every attempt is listed in the app with the status code your server returned.
  • ImprovedHours over the API are computed the same way the payroll export computes them: real elapsed time between two instants. The night your clocks go back reads as thirteen hours there too.

Credential wallet & exclusion screening

  • NewStaff can upload their own credentials. The wallet belongs to the person, not the employer: she uploads a licence once, renews it once, and every facility she works for sees the current version. Employers can read it; they cannot edit or delete it.
  • NewFederal exclusion (OIG LEIE) screening. A confirmed exclusion blocks scheduling outright. A possible match blocks scheduling until a human resolves it: names on the public list collide, and that adjudication belongs to the employer, not to software.
  • NewThe credential library now names what a surveyor actually asks for: 22 types across licensure, certification, health screening and background checks.
  • NewFill waterfall. An open shift escalates through your own staff, then the float pool, then your other locations, and only then suggests an agency, with the agency spend it avoided shown as a number.
  • ImprovedAgency staff are now costed at their bill rate rather than an internal wage, so the true cost of covering a gap is visible while the decision is being made.

Rules engine & schedule grid

  • NewThe scheduling engine: thirteen rules checked on every assignment: double-booking, minimum rest, shift length, consecutive days, weekly and averaged hours, ACGME duty windows, credentials, skills, position, time off, availability, employment status.
  • NewInteractive schedule grid with live conflict checking as you drag, coverage bars, labour-cost ribbon and undo.
  • NewLive demo at /demo: the real scheduler, on a real unit's worth of staff, with no signup.
  • ImprovedAll durations computed on real elapsed time, so a 19:00–07:00 night shift is eleven hours on spring-forward and thirteen on fall-back. Overtime, labour cost and payroll export all agree.
  • FixedDeleting a user account failed on a foreign-key violation: a user's own audit trail pinned their account in place forever, which made account deletion and data-erasure requests impossible. Audit history now survives the person, with the actor forgotten.

Watch us ship

Every entry here is dated, specific, and describes something you can go and do in the product right now. Start with the credential blocking; it is the one nobody believes until they try it.

Open the live demoStart free trial