Stream: implementers
Topic: Patient reported procedures and screenings
Daniel Tam (Aug 19 2021 at 18:33):
How is US Core identifying patient reported procedures and screenings? Is this using the Procedure.asserter field, and filling this in with the reference Patient?
In my organization, we partner with different health systems. For the purposes of quality reporting, some of these health systems allow patient reported data without further documentation (i.e. "Yes I had a colonoscopy screening six months ago")
But other health systems are stricter and will only accept procedures that include documentation from the originating provider (i.e. an accompanying fax, or a C-CDA, etc).
We are a primary care facility, so many of these procedures / screenings are performed by a third party, with who we may or may not have interoperability worked out. As a result we have a mix of patient reported and also fully documented procedures and screenings.
Just wanted to ensure I flag these patient reported screenings correctly. If there's already a thread for this could someone point me that way?
Michele Mottini (Aug 19 2021 at 18:42):
You can surely use asserter, but it is not a 'must support' for US Core, so it is likely that clients will ignore it. I don't think US Core really covers this generic user-reported case, it has support for user-reported medications
Michele Mottini (Aug 19 2021 at 18:42):
(You can ask in #argonaut or #united states )
Morten Ernebjerg (Aug 20 2021 at 05:56):
I'm working in the European context, so I don't known what the guidance/common use is in the US. But we have a similar situation in our system (mixed "official"/patient-reported data). I was wondering if this could also be solved using Provenance. Provenance is profiled in US Core, with agent.type and agent.who being must-support. So for patient-reported source, one could add a Provenance resource with an agent entry having type = "author" and who pointing to the Patient resource, to indicate that the patient is responsible for the information in the target resource. If I read it right, this seems to match the Health Information Exchange (HIE) use case from the US Core basic provenance page.
Of course, this all requires such Provenance resource to be (consistently) available, plus all systems have to search for matching Provenances rather than just looking in the resource itself when they want this information.
Last updated: Apr 12 2022 at 19:14 UTC
