Hacker News new | past | comments | ask | show | jobs | submit login

> For example, today's AB- would become +HAB-R for "has H,A,B lacks Rhesus factor."

That's already the way A, B, and Rhesus factor work. The abbreviation for Rhesus factor is "+", but the formal terminology is "Rh+". I would have expected "H-" by analogy.




> That's already the way A, B, and Rhesus factor work.

No, it isn't: The current ABO system is incapable of expressing "null" data (e.g. "we don't know if B antigens are present or not") and relies on implicit "no marking means false" assumption, which becomes a problem if a new/newly-important antigen feature is discovered, or if a new variation of an existing antigen is found.

For example, suppose we discover a new type Z, which is a membrane-sugar just like A and B, and logically ought to be encoded the same way. It exists in a 50/50 ratio in every existing blood-group, and it finally explains some rare but fatal transfusion problems.

Now some unconscious patient arrives at the emergency room with a wristband saying "AB+". Does that string mean they were tested for Z already, and it was absent, or does it mean there no data about whether Z is present or not? Nobody knows! Worse, if you do a test and discover no Z, then you write the same thing and have the same problem later, all because of the mistake of encoding "false" as an empty string.

Now you might say "Forget the ABO crap, require Z+ or Z- to appear as a separate item", I'll say: "I totally agree, but let's remove the ABO crap and encode all the antigens the same way to make it logically consistent and clear."

> I would have expected "H-" by analogy.

If you're thinking of another section like "A Rh+ H-", then that's close to what I'm proposing, except that it hasn't fixed the historical ambiguities of O/A/AB.

If you fix it to make things explicit and consistent, it becomes "A+ B- Rh+ H- ", and if you shorten Rh to R and group similar things together... that leads to codes like +R-HAB or -ABH+R, which are (ordering aside) what I just proposed.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: