...
- Best practices and recommendations
- standardization of data and data structure and requirements (Karly Rowe)
- USCDI R2 in progress
- USPS address standardization (publication 28)
- Carmen Smiley to write up our position on this, which is it is complex and we do not have specific recommendations, but here is a list of ongoing/upcoming efforts to keep an eye on
- IAL
- do we want to make any recommendation on minimum IAL that organizations should put into their agreements when implementing these solutions together? Julie Maas Catherine Schulten
- Logs and Audits
- Responder to log information on non-match scenarios for further analysis
- Requester to log information on no results/non-matches although they won't have the same level of information on why there wasn't a match as the responder
- Use of Only Certain Matches flag in FHIR patient match operation
- use cases when this should be set to true or false
- definition of "certain match" - what is the threshold?
- Comparison of Solutions
- Adjusted Technical and Process complexities based on feedback from Blake Hall
- Meena Jambulingam to write up/tweak intro to solutions to indicate use cases when one or more solutions may be applied either individually or together
- Meena Jambulingam extend FHIR patient match operation to add IAL in request
- Call out that solutions 3 and 4 don't necessarily preclude participation in/of multiple trust networks
- Collin Wallis - establish a NIST 63-3 "healthcare profile" - this is probably a good addition in scope to whatever happens next with FAST
- From Eric Heflin to All Panelists: 04:06 PM - 1) human-mediated identification. In which case a lower standard of traits may be of value because the human can disambiguate. 2) if the system is automated then we may need to have either "one or none" matching as desired.
- From Abel Kho to All Panelists: 04:07 PM - There is not a single answer here because there are different intents for why you want to match
- From Paul Oates to All Panelists: 04:07 PM - yes, seeing some energy for a "floor" but not a consensus on whether we can set that. something we need to pursue in further discussion as a topic I think. until then, looks contextual
- From Abel Kho to All Panelists: 04:08 PM - If in B2C someone wants to access their data or a service, they will be willing to provide high quality data or an authentication token
- From Eric Heflin to All Panelists: 04:08 PM - @Matt, if a human is disambiguating the patient list, then we don't need a yes/no answer for the first list returned of candidate matches.
- Solution 2: If we’re going to scale demographic matching nationally, you need to find centers of service to get it done – can’t do point to point
- Agree, wasn’t thinking point to point or even regional – need to think about nationally
{"serverDuration": 44, "requestCorrelationId": "676b99dd38903d7d"}