They actually have a huge Elixir project in Ukraine, it was used to reform and digitalise the healthcare system.

It’s also open source https://github.com/edenlabllc/ehealth.api

Here’s a talk about it:

I have been working on EMR system Helium Health and whole application is written in Elixir. I also have been working on FHIR implementation in Elixir, but since then I have switched the job.

My brother (family physician) and I started a direct primary care practice in South Carolina. We ended up building a lot of tools to run the practice and now sell them at https://scalpel.com/. We handle note taking, scheduling, internal/external communication, patient surveys, invoicing, online booking, and more. So there are at least two EMRs built in elixir. @darkmarmot let me know if you want to chat more about what we’re doing.

I work at a healthcare-related company, ScriptDrop that runs on Elixir. We coordinate couriers & pharmacies to get prescriptions delivered to patients. We don’t have a ton of open-source stuff at the moment, but there is this little library:

We use it to handle the “signed overpunch” format that NCPDP D.0 transmissions use for some fields.

We started out using Phoenix + Elixir as “fast Rails” with some extra binary-protocol-handling goodness for D.0. We’re now getting into more Elixir-y things with GenStateMachine.

This is an interesting perspective. For me it’s the opposite way around.

For low-level details of the code, mutability and direct pointer references make some things much easier (for example, everything having to do with graph algorithms, DOM manipulations, etc). I know because I’ve tried to do these things in Elixir and they are a pain.

However, for higher level program logic, elixir’s immutability seems like a positive thing, although probably less performant.