Hi, everyone
I realised I started this topic, and just disappeared. Shame on me!
I think both Ianās and Heatherās template will work. And Ianās is already in use, I suppose. My comments:
First, the COMPOSITION:
I like the new Certificate COMPOSITION, as linked to the CKM above . There are a lot of use cases for certificate: Death certificate, Birth certificate, Medical condition certificate (i.e. needing assistance), Medication certificate (i.e. bringing opioid medications with you abroad and prevent you from being arrested for drug traffic), Vaccination status, Stating you are fit to (still) drive a car, etc. Keeping certificates apart from other COMPOSITIONS is a wise thing to do, IMO. Likewise to add elements relevant to the certificate within that context is a good idea, i.e. the certificate issuer, validity, ā¦
I donāt know if it should be only one general certificate COMP, and specialize them, or having more specific certificate COMPOSITIONS. Any thoughts on that?
Secondly, EVALUATION.Immunisation_summary vs ACTION.medication-vaccination:
I see that the health service provider need an ACTION to record that a specific vaccine has been given. I might demonstrate my lack of understanding, but is it the ACTON that leads to the vaccination certificate? The ACTION.medication is for recording a given medication, regardless of if it is a vaccine or another product. It even says so in the Concept description.
Shouldnāt the ACTION populate a persistent archetype which keeps track of which number in a (potential) sequence of jabs, and when the next vaccination is due? This is what the EVAL.Immunisation_summary does.
It would be nice to agree upon how to deal with vaccinations within the community. I fear that implementations are deviating, and will cause trouble later.