FHIR Consent IG - December 4, 2015
Notes of email December 4, 2015
Hi FHIR Consent Directive community
I have successfully created a Privacy Consent Directive IG. I pulled in the introduction from the CDAR2_CD_IG, and adjusted it minimally to say FHIR rather than CDA… since that introduction had the USA use-cases, I added the Canadian use-cases we got from Pat. Review and suggestions on this material are VERY WELCOME…
You will notice that I followed a template for an IG (thanks to Keith). Thus there are placeholders for Actors, Profiles, Extensions, and Value Sets and Terminologies. I removed Operation as I didn’t see that we needed it, but it might be…
For Actors I guessed at Writer, Reader, and Enforcer. But there is nothing behind these thoughts… pages need to be written if we want Actors. Note that having Actors is critical to Conformance claims as it is only at the Actor level that one can claim conformance. Conformance claims are not done to the Profile, they are done to the Actor… this is my current understanding.
I pulled in the existing Consent Directive Resource Profile in (likely people are not going to like “Basic Privacy Consent Directive”, but this way I force people to read and comment), and left placeholders for other profiles we might want…
- I did modify the profile, specifying that subject must be a Patient; and that type must be a consent directive. I think this is what we want, but mostly I did it to test the use of the Forge tool that is now used to modify the profile.
- MANY improvements need to be done to this. We need introduction, notes, etc… we need better descriptions… we need to add vocabulary.
I left Extensions in, but don’t think we have any yet… although Pat was speaking to a potential need if the elements of Contract are not filling our need.
Seems Value Sets and Terminology are likely the next thing we need to start building. This is where we would specify our valuesets that are specific to consent, not contract. Yes, they should be harmonized vocabulary; but I think we should build them first and ask for harmonization before we leave DSTU.
I also put in the examples I wrote from the Canadian use-case examples, so they have been fixed and you can now read them in JSON if you like. You will find these on the Contract Examples page. Again, comments WELCOME.
So, your homework is to review this and have comments for us to ‘improve’. Again… Improvement opportunities are HUGE.
You get to the IG by going to the current build http://hl7-fhir.github.io/
And clicking on the “Implementation Guides” link in the bottom section of the home page, under Implementation”.
You can also get there from the Contract page, but need to go through Examples. I will look into why it no-longer shows up as a Profile…
You can get to the IG directly: http://hl7-fhir.github.io/pcd/pcd.html
