Stream: netherlands
Topic: LIR
Michael van der Zel (Feb 21 2018 at 08:08):
I am strugling a bit with a registry that says it does FHIR, but in reality it does not. Well.. It uses REST and JSON, but for someone to state they use FHIR, my opinion is that they SHALL use FHIR resources and actually the full FHIR REST spec. Right?
Grahame Grieve (Feb 21 2018 at 08:21):
the minimum you need to do is return a capability statement, and do what it says.
Michael van der Zel (Feb 21 2018 at 08:35):
Thanks. I'll ask them.. :-)
Michael van der Zel (Mar 01 2018 at 10:40):
The registry is not allowed to receive patient information. What is the best way to handle this? Create a Structure Definition on top of the Resource and restrict the patient (subject) references out (mask them) or pseudonymize it?
John Moehrke (Mar 01 2018 at 13:07):
This is a case where this system needs to receive de-identified data? Would love to work with you on how you do this. I do suspect a good start is to use a StructureDefinition to define the chosen algorithm. The agent that does the de-identification on an object, could then tag it as having been de-identified and indicate the canonical URI of the StructureDefinition to indicate so. Easy algorithms are replace an element with a fixed value (e.g. "removed"), but even that likely needs extensions in the StructureDefinition. See http://build.fhir.org/secpriv-module.html#deId
Michael van der Zel (Mar 07 2018 at 08:12):
I first have to convince them that doing REST and JSON is not equal to doing FHIR :-(
Last updated: Apr 12 2022 at 19:14 UTC
