Stream: Da Vinci/plan-net-connectathon
Topic: Signup Sheet?
Tone Southerland (May 15 2021 at 12:47):
Is there a sign up page for this track? I don't see a link on the track page https://confluence.hl7.org/display/FHIR/2021-05+Da+Vinci+Payer+Data+Exchange+Track+for+CMS+Patient+Access+API. We are also testing in the CARIN BB IG Track (as a consumer app)...
Shaheer AbdulKareem (May 18 2021 at 21:29):
Our Provider FHIR Directory API implementation have a hard limit of 30,000 on total number of resources can be accessed through multiple paginated calls of the same request. Our Provider FHIR directory API is implemented using the "transformation" approach on top of our legacy provider service. Anyone know if this limitation violates any CMS mandates? If yes, what use case will be not handled by this limitation? @Saul Kravitz @Robert Little
Saul Kravitz (May 18 2021 at 21:34):
@Sean Mahoney
Sean Mahoney (May 19 2021 at 14:04):
Tone Southerland said:
Is there a sign up page for this track? I don't see a link on the track page https://confluence.hl7.org/display/FHIR/2021-05+Da+Vinci+Payer+Data+Exchange+Track+for+CMS+Patient+Access+API. We are also testing in the CARIN BB IG Track (as a consumer app)...
Tone, we do not have a sign up page that I know of. But thank you for attending our track!
Sean Mahoney (May 19 2021 at 14:39):
Shaheer AbdulKareem said:
Our Provider FHIR Directory API implementation have a hard limit of 30,000 on total number of resources can be accessed through multiple paginated calls of the same request. Our Provider FHIR directory API is implemented using the "transformation" approach on top of our legacy provider service. Anyone know if this limitation violates any CMS mandates? If yes, what use case will be not handled by this limitation? Saul Kravitz Robert Little
Shaheer, the rule states that payers maintain a publicly accessible standard-based Provider Directory API described at § 431.70 which must include all information specified at § 438.10(h)(1) and (2). That includes information for all active providers.
Shaheer AbdulKareem (May 19 2021 at 15:09):
Sean Mahoney said:
Shaheer AbdulKareem said:
Our Provider FHIR Directory API implementation have a hard limit of 30,000 on total number of resources can be accessed through multiple paginated calls of the same request. Our Provider FHIR directory API is implemented using the "transformation" approach on top of our legacy provider service. Anyone know if this limitation violates any CMS mandates? If yes, what use case will be not handled by this limitation? Saul Kravitz Robert Little
Shaheer, the rule states that payers maintain a publicly accessible standard-based Provider Directory API described at § 431.70 which must include all information specified at § 438.10(h)(1) and (2). That includes information for all active providers.
Thanks for the response @Sean Mahoney
The API do provides information for all the providers for every "meaningful searches". The limit gets enforced only when a request attempt to go beyond the 30000th resource. This is put in place for performance & also to limit "bot attacks" trying to capture the entire data by paginating through millions of resources. Does "includes information for all active providers" really means the api have to support providing the complete provider list with the same request through pagination? It seems like the rule is not that precise. I am still wondering what use case will this solve.
Sean Mahoney (May 19 2021 at 16:56):
Shaheer, The Plan-Net IG does specify the $export asych function, which would provide the entire provider directory. This provides 3rd party developers the ability to cache and store directorie
s for performance considerations.
Last updated: Apr 12 2022 at 19:14 UTC
