Data at the Point of Care (DPC) Community
Hello DPC Community,
On Tuesday, 4/27 from 2:00-3:00p EST, the DPC team will be holding office hours to solicit community feedback on upcoming API changes related to FHIR R4 and the DPC API in general.
We are excited to meet with you all to discuss your thoughts about the API and how we can best meet your needs and expectations.
We appreciate your continued cooperation and curiosity in the process. Information on how to join the DPC Office Hour session will be posted closer to date.
Thank you,
The DPC Team
Data at the Point of Care (DPC) Community
Hello DPC Community!
Below is the Zoom joining information for the DPC Office Hour on Tuesday, 4/27 from 2-3PM EST.
During this Office Hour, we will discuss and answer your questions on the upcoming API changes related to FHIR R4 and any other topics of your interest.
If you are unable to make it, we will be posting a follow up with notes about what topics were addressed during the Office Hour.
Thank you all and we look forward to seeing you tomorrow!
——
Join Zoom Meeting
https://zoom.us/j/93075202333?pwd=NlBwbG1PamJ0OVlBRHdsTDhkU0xHUT09
Meeting ID: 930 7520 2333
Passcode: 654251
One tap mobile
+13017158592,,93075202333# US (Washington DC)
+16468769923,,93075202333# US (New York)
Dial by your location
+1 301 715 8592 US (Washington DC)
+1 646 876 9923 US (New York)
+1 312 626 6799 US (Chicago)
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 408 638 0968 US (San Jose)
Meeting ID: 930 7520 2333
Find your local number: https://zoom.us/u/aXrceooHL
Payal Patnaik
Data at the Point of Care (DPC) Community
Hello DPC Community,
As promised in the 4/27 Office Hour session, here are the relevant notes and topics that were discussed in the session. Please respond to this thread if you have additional comments or questions on what was discussed.
As always, thank you everyone who was able to join! The feedback that you gave in the session was invaluable and will be used to make sure the API is as user-friendly as possible.
Best,
The DPC Team
These are the questions that were asked during the office hour:
- DPC vs BCDA: Is there a limit to the amount of historical data that can be returned from DPC?
- DPC returns as much data as is available from our data source (BFD), approximately since 1/1/2013.
- DPC technical, _since function: We utilized the _since parameter and did NOT see significant gains in improvement. Are there other best practices?
- I would highly recommend getting into a cadence of using the _since parameter once you have caught up with a given patient. Make a complete historical call. Then, make _since calls to keep up to date.
- For more information, please reference the DPC documentation on this topic.
- DPC Attribution: Are there recommendations or guidelines on what DPC is looking for as evidence or examples of how we attribute patients to practitioners? Should we do a written explanation or python script?
- We will check whether there is a claim in the last 18 months for that provider with the data. A written explanation is definitely sufficient. We will continuously run checks to see whether the data is being used.
- FHIR R4: Regarding migration to FHIR R4, is this only the outputs from you (DPC), or will our inputs need to be in R4 format as well?
- We do not have a specific answer yet, but we will have guidance on this published soon.
- Credentialing, ACO’s and Integrators: I work for a health IT solution that works with many ACO’s (MSSP ACOs). Should we be credentialing through DPC in a special way?
- During the application process to the pilot you will be asked to specify which partners you are working with; we will check with those partners individually. Each provider group must be credentialed individually even if you manage multiple provider groups or ACOs.
- DPC technical, _since parameter, synthetic data: Testing the _since parameter in the SBX environment is not intuitive. Will this be improved soon?
- DPC is working to improve our documentation now, and we hope some of the new changes will make this process more intuitive.
- Is there a specific date that the _since parameter is checking against that we could use to double-check?
- The _since parameter uses the lastUpdated field as a checkpoint for claims.
- The lastUpdated information should be located within “meta” in DPC payloads.
- Improving our synthetic data is on the roadmap and actively being worked on.
- R4, Release: Is there a more specific date we should be prepared for and testing?
- No more specific than summer. Keep track of the Google Group and your email for news as we move forward.
- Technical, _since, dates: Could the lastUpdated date for the synthetic data be set to match the claims date?
- We will pass this on to the team responsible for updating DPC synthetic data.
- Technical, _since, date: How is the lastUpdated date changed? What does it mean?
- It should not. If it does, we would consider that a bug, and it would be fixed so that claims did not have their lastUpdated dates altered.
- If there are new claims that come in, they will have a new lastUpdated date. Old claims will not have their lastUpdated date changed.
- Can we share data from one provider to another provider?
- Check with your organizations’ Privacy Officer. DPC guidance recommends that you return a provider's data only back to that provider.
- What about new patients that do not have any claims during the 18 month lookback period?
- We are aware of the limitations of 18 month lookback and are currently assessing how that affects the new patient use case.
- Are the other DASG APIs, such as Blue Button, migrating to R4 as well?
- This migration should occur around the same time (summer 2021) for all four APIs: BCDA, DPC, Blue Button, and AB2D.
- We are trying to understand if data is from the physician billing side versus the hospital billing side. Are there any flags or fields in the DPC data that we could use to tell?
- Eob.type.coding[N].code
https://bluebutton.cms.gov/resources/variables/nch_clm_type_cd/ - We do not have a flag to distinguish between professional billing and hospital billing that would match with your specific EHR. But, we do have fields that can tell what type of claim it is and that may help you categorize the claims.
- We match using the provider NPIs and the date, at this moment.
- Eob.type.coding[N].code
- Medication: Is there any relationship between the medications prescribed in a visit and the claim where it was prescribed?
- No ordering information is present in claims, and there are no direct links between medication claims and the claim for the encounter in which the medication was prescribed. Users may be able to make connections between claims based on dates, but DPC is unable to directly support that data analysis.
