https://tangled.org/joelparkerhenderson.com/architecture-dec...

https://tangled.org/joelparkerhenderson.com/ways-of-working

https://tangled.org/joelparkerhenderson.com/coordinated-vuln...

My wishlist: free for open source and paid for closed source, able to do simple projects that are handwritten and also complex projects including AI LLM code that needs CI/CD/auditing, and hosting in the UK or EU.

Aside, I donate money to Codeberg because I think Codeberg is a wonderful service with strong commitment to free open source, and because I host some larger projects and AI projects that are for public welfare social good.

Self-promo links below if you would like to star a few of mine good for developers.

https://gitlab.com/architecture-decision-record

https://gitlab.com/ways-of-working

https://gitlab.com/coordinated-vulnerability-disclosure

ER7 message parsing Rust crate:

https://crates.io/crates/er7

I'm seeking advice about what would help improve the README examples, to make it easier or better to use in your own HL7 health care projects.

Source is https://github.com/er7-rust/er7-rust

Comments URL: https://news.ycombinator.com/item?id=49318858

Points: 2

# Comments: 0

For example: The standard FHIR $export operation can support extensions that take de-identification config details as additional parameters. The standard openEHR can query then return non-id fields. The standard SNOMED codes can be rolled up e.g. high-specificity codes can be aggregated into a low-specificity code.

But: for compliance/legal/auditing reasons, all organizations that I know of personally do not rely exclusively on these protocols for de-identification. Instead, the organizations place their de-indentification processes in a kind of "clean room" that does many more kinds of cleansing, redacting, aggregating, chaffing, filtering, and the like.

Fast Healthcare Interoperability Resources (FHIR) using Rust:

https://github.com/fhir-rust/fhir-rust

Open Electronic Patient Record (openEHR) using Rust:

https://github.com/openehr-rust/openehr-rust

Systematised Nomenclature of Medicine (SNOMED) using Rust:

https://github.com/snomed-rust/snomed-rust

I have work in progress creating stores for PostgreSQL, SQLite, MySQL, MariaDB, MSSQL, Oracle.

- Project portfolio management software. Good results so far. This is unguided experimentation: Fable researches feature ideas and plans them, then Opus 5 implements them, without me in the loop. The features include things such as an auth server, full-text search, audit logging, resource leveling, HA/DR, IaC, and more.

- FHIR & SNOMED medical software experimentation in demo-only environments. This has mixed results so far. This is guided experimentation: the FHIR specifications and SNOMED specifications are thorough and I'm in the loop. Fable plans OK, but Opus 5 is thrashing a lot, going down many rabbit holes.

My longtime friend has MS and she does community outreach about it, but someone on Facebook has stolen her identity. Facebook support channels are beyond her ability.

Can you help me help her? My email is joel@joelparkerhenderson.com. I can afford to pay $100 or donate to your favorite charity. Thanks in advance.

Comments URL: https://news.ycombinator.com/item?id=49022700

Points: 3

# Comments: 0

This sounds like a back door. Is it?

To me, the whole article feels super-unclear about what exactly is involved.

Can HN folks who know more weigh in?

I'm creating a health economics rust crate that has many of the calculations, and I'm seeking feedback from people in the field on how to improve it.

https://crates.io/crates/health-economics

https://github.com/joelparkerhenderson/health-economics-rust...

Comments URL: https://news.ycombinator.com/item?id=48958292

Points: 1

# Comments: 0

http://github.com/joelparkerhenderson/queueing-theory

https://github.com/software-engineering-guide/software-engineering-guide

I'm seeking recommendations and constructive criticism please, for this first draft. Much of the guide is AI-LLM generated, with me proofing and guiding the content.

Comments URL: https://news.ycombinator.com/item?id=48834490

Points: 1

# Comments: 0

https://lilydesignsystem.github.io

I understand the point of that for unknown accounts; perhaps you could consider faster FTUX by leveraging my other existing social accounts? E.g. GitHub, GitLab, Codeberg, LinkedIn, Reddit, etc. And/or enable me to browse public accounts or example content in the meantime?

If anyone from OpenUI would like to connect with me to add Lily, please do, joel@joelparkerhenderson.com.

A gate is best when it's proportional to what goes through it. Small project? The business case is "Pam thinks it's could be a good idea". Large project? The business case is a formal study. The word "proportional" makes it much easier for all the participants to understand that the gate is a sliding scale.

Even more important: stop using personas, start using actual people. I've experienced many startups make unforced errors by conflating people into personas. A better way is to tag people with attributes, such as specific interests, explicit concerns, tasks to be done, usage goals, learning preferences, and the like.

When you switch from personas to actual people, it opens up many more product experiments-- many of which are surprising and may even feel counter-intuitive to founders. Increase your startup chances of success by carefully connecting with your actual users.