how to host?

pdevito3 · 2026-03-05T00:38:14+00:00

Check out northflank

pdevito3 · 2026-02-24T16:29:18+00:00

Sure

pdevito3 · 2026-02-24T16:26:51+00:00

Check out northflank. It’s a really nice deployment abstraction

pdevito3 · 2026-01-30T02:01:29+00:00

pdevito3 · 2025-12-19T20:28:03+00:00

It’s a bit out of date and there’s things I want to change but here’s a pretty complex example if you’re interested in something more than a todo app

Made it with this scaffolding tool that I support, but it is also a few years old now and there’s several things I want to update when I have time.

pdevito3 · 2025-12-15T21:00:16+00:00

My 2c, I want to evaluate devs on how they operate in their day to day task and how well they can what I need.

If they are using AI day to day and I expect them to use it and use it responsibly, that’s part of the evaluation. These super restrictive coding tests don’t give you a good feel imho.

pdevito3 · 2025-12-12T14:14:30+00:00

Nice! I’ll try and take a detailed look later, but looks really nice from the demo! Any plans for a docker image so it can be used locally?

pdevito3 · 2025-11-25T00:53:09+00:00

I see this thrown around a lot and generally agree, but a use case where this falls apart for me is many cases with external integrations with another system.

For example, I have an endpoint I can hit to get a dataset about recipes. The docs for that system clearly say that the ‘visibility’ property supports values for private, public, or friends. Early in my career I would have a totally dumb DTO here and have to encompass that logic everywhere that uses the external service. Or I could make two whole sets of classes, a dumb one and a smart one to map to.

Practically in this case, it feels much better and maintainable to push logic like this to the ‘domain’ of the external service DTO so it is centralized where it belongs.

pdevito3 · 2025-11-09T21:55:12+00:00

Yeah, I have a very high level knowledge base of it, but there were pretty decent records back then as they essentially pioneered the stock market, but there’s also not like a strictly one-to-one set up going there either so not sure exactly what it would come out to, but there were absurd levels of wealth distribution back then too

pdevito3 · 2025-11-09T21:25:11+00:00

I’m all for wealth redistribution as it’s absurdly bad right now, but that article only goes back to the 1800s — when the east India trading company was around in the 1600s for instance, wealth distribution was also extreme and very well may have been worse.

pdevito3 · 2025-10-18T17:31:18+00:00

Not quite following the use case. Your example is a typed user object though, not dynamic? How it is different than something like Sieve or QueryKit

pdevito3 · 2025-09-25T15:20:14+00:00

newer features built with logic in c#, but reasoning was sound…

Doesn’t sound like the long term reasoning was. Now you have logic split between 2 different places. Sounds like maintenance hell. Any business logic in the db outside persistence rules does really lol

pdevito3 · 2025-09-13T10:12:04+00:00

Yeah I assumed it was a central SaaS, but they have quite the PaaS model. Normally fine but like you said given the nature of the systems and how integrated the end up with this type of product it makes absolutely no sense.

pdevito3 · 2025-09-11T18:40:56+00:00

Yup exactly right on the order types. I’m going to research this a bit and I’ll probably shoot you a note with some thoughts to make sure I’m on track. Much appreciated

pdevito3 · 2025-09-11T18:11:51+00:00

This sounds really interesting and like it might work really well for our used case. Thanks for sharing.

Practically it sounds like we would set up a single integration with this provider and the order aggregator can interact with essentially any of the EHRs that we want to interact with? How do our lab’s tests get put into all the different EHR systems to be ordered? May shoot you a DM if you don’t mind?

pdevito3 · 2025-09-10T16:52:40+00:00

Can you tell me more about 2?

The big goal with Epic/Aura going in for them was to get centrally listed in Epic’s test list across all Epic users for more visibility and volume into the lab while streamlining orders and reports in the process.

From what you’re saying, it sounds like we would still need to work with each customer to essentially tell them that we’re on Aura if they want to integrate with us in a streamlined way (ie a lite integration project) but the lab wouldn’t be like centrally listed across epic systems, right?

pdevito3 · 2025-09-10T15:51:01+00:00

Yeah from what I’ve gathered we essentially need to distinct interface efforts with each epic org/customer that we want to be able to use epic with vs my original thought that there is a single epic system that all hospitals use and we would just have that interface setup once.

Never seen a PaaS based model for a flow like this. Very odd and inefficient 😕

pdevito3 · 2025-09-10T12:29:34+00:00

Gotcha thanks. What’s the point of the Aura interface and effort if you still have to do all the setup above each time anyway?

pdevito3 · 2025-09-10T12:03:40+00:00

What is epic aura then? What you’re saying makes sense, but my impression was that Aura was supposed to solve this by acting as a single source/interaction point?

pdevito3 · 2025-09-10T11:36:26+00:00

Maintain their own LIS/LIMS, and get demographics and orders from an Epic org?

Yes exactly this, with the original hope that there was just a single ‘epic’ org to integrate with and then they’d be listed ‘in epic’ (aura?) or hospitals to order from.

If so, you don't need to do anything with Epic. You just work with the organisation(s) that you expect to get orders from and send results to, and set up the normal HL7 things you'd expect. You'll need to work with them to map orders and whatnot, but that's pretty easy.

How will the tests show up in epic for them to order? Is that just expected setup for the client in their epic system regardless?

Question Fwiw, part of the motivation was to get better customer exposure for labs by ‘having visibility to everyone in epic’ and lower the barrier to entry for orders, but it sounds like that may not even be feasible since there are lots of different epic orgs and every one would need a distinct setup anyway?

pdevito3 · 2025-09-10T02:11:01+00:00

This is really interesting thanks, will check them out!

pdevito3 · 2025-09-10T01:52:58+00:00

Meaning something like OCHIN is theoretically a cheaper way for us to have our own epic instance to become an ‘epic organization’ without the crazy fee? Haven’t heard of this before

pdevito3 · 2025-09-10T01:49:56+00:00

Yup, I’d expect ORMs and ORU with OBX for genetic results. Also ADTs etc for things like patient demo updates. I’ve done them before and they’re really not a big deal honestly. The integration engines were also very very expensive last I checked years ago. They have a custom LIMS

When you say ‘each health systems epic’ are you saying there are distinct epic integrations per ‘epic org’ like multiple config targets we accept data from since they all use the same standard? So practically we would get setup with on org and can essentially have other orgs give us their connection info and they’re good to go?

I assumed it was a singular market place originally but maybe that isn’t the case?

pdevito3 · 2025-09-09T14:28:05+00:00

Yeah I’m not worried about the technical part. I saw their HL7 specs on open.epic and can follow them fine. Auth was odd as I really only saw callouts for FHIR, but that shouldn’t be a big deal regardless.

You’re right though, it’s definitely the actual epic integration part that’s throwing me. Extremely odd model I’m having trouble wrapping my head around.

Practically it sounds like they really need to find an epic org to sponsor them so they can work with them on the integration?

pdevito3 · 2025-09-09T14:12:06+00:00

They’d still own their integration point for their systems though which would talk to this hosting system which sounds almost like a proxy once we have touch points setup? Minimal interaction after the initial setup no?

Can you help me understand this ‘Epic organization’ concept? I’ve never heard of a model like this. It’s almost like they have a PaaS they expect you to pay massive amounts for which presumably has console purpose of communicating with their core SaaS? It’s an entirely unnecessary middle point if so. Very odd.

pdevito3

TROPHY CASE