Stream: implementers
Topic: data accuracy
Susheel Palakurthi (Jul 10 2021 at 23:48):
Hello everyone!
I was wondering if anyone is focusing on the area of data accuracy, specifically data obtained from other provider/entities' APIs of the healthcare system and how you're handling any such case like so
Susheel Palakurthi (Jul 11 2021 at 00:14):
In any case, also wanted to check in the industry and get to know what others are working on with FHIR and other healthcare/healthtech systems -- whatever you're willing to share, aha :thinking:
Lloyd McKenzie (Jul 11 2021 at 02:08):
Can you explain what you mean by accuracy? What exactly are you trying to measure?
Susheel Palakurthi (Jul 11 2021 at 02:24):
Lloyd McKenzie said:
Can you explain what you mean by accuracy? What exactly are you trying to measure?
While we were doing our research on the FHIR APIs, we got to know some problems with the current implementation guide and features. For example, when accessing any data, how can we be sure about the integrity of the data? Ex. an insurance provider enters the physician's name for the name of the organization/clinic. Or is there data validation we can do on our end, as 3rd party apps?
Lloyd McKenzie (Jul 11 2021 at 02:56):
There isn't typically a lot you can do. If you have multiple sources, you can cross-check the data, but it's possible for multiple sources to have the same error if the data originated from the same original source. If there are specific rules that can allow you to reliably check string values, you can try that. You can also do sanity checks on dates and numeric values.
John Moehrke (Jul 12 2021 at 12:07):
not uncommon for a recipient to consider the source. but that is business rules, not something that would show on the interop standard.
John Moehrke (Jul 12 2021 at 12:08):
There is a way that a sender can declare a level of integrity, they could tag the data with .meta.security element using the valueSet that has a bag of integrity statements -- http://hl7.org/fhir/v3/SecurityIntegrityObservationValue/vs.html
this is not typical, and is a decaration the sender would be expected to place on the data. (The recipient could decorate the data upon receipt too, possibly using some algorithm).
Jose Costa Teixeira (Jul 12 2021 at 15:12):
I would hope to handle data quality in meta, but not in security.
Jose Costa Teixeira (Jul 12 2021 at 15:13):
One foremost case for data quality is MeasureReport
Last updated: Apr 12 2022 at 19:14 UTC
