Even I could understand this I loved it .
Great! Need to add the other two programs: Education and Software.
They’re under the “4” next to “Programs”.
Here’s the Xmind file if anyone wants to play around with it:
openEHR.xmind (227.3 KB)
By the way, some time ago someone in the community made “mug” archetypes and I know a few people who bought it (I don’t really remember who made the mugs), but it’s probably my most precious openehr possession
I will try to do a panoramic photo from it
@johnmeredith was that you?
John is off sick apparently but I am pretty sure he was responsible for the Mug archetype.
I
We could re-do a similar concept though
…or use the actual, published archetype OBSERVATION.fluid_input:
I love this Beverage one - just a bit quirkier than a ‘proper’ archetype.
In the context of a mug, the Fluid input one is rather quirky too…
Btw, here are Xmind files for both of them:
Fluid input.xmind (79.1 KB)
Beverage intake.xmind (86.1 KB)
Yup - in the context of a mug - I get it … eventually!!
@heather.leslie brilliant! But we need a wine one as well. I know it’s in good hands.
Don’t forget beer… so many options!
Wonderful, Shinji! You should make a T-shirt with that. I would love wear it at HL7 meetings.
Actually it was Hildi My idea but she built the archetype.
I would change “Milk type” to “Creamer type” (“Supplementary fluid type” is too long) … oat and almond are not milk
Hmm, rationally Blood pressure archetype, amazing to see version Hx, review results and translations. It’s also an excellent example of why openehr is closer to clinicians as it represents unit of clinically relevant model with contrast to using a FHIR profile with multiple Observation resources.
You are right, it makes most sense and for people outside the community/congregation it will be more recognised. Internally, I guess we’re a bit tired of the BP archetype, and want to promote something new and funny. Let’s do as Winnie the Pooh and say “Both, please”.
In that case my second preference would be Adverse Reaction Risk. As I recall we worked with the FHIR community to create this one which at that time resulted in a carbon copy Resource. Not sure if they went separate ways afterwards.