2022.05.13 EQRS EDI Touchpoint Status Meeting

Vaccinations:

Any questions on documentation, file structure, XSDs, XML, data dictionary, prod-preview readiness, questions in the UI?

What kind of progress has been made with the vaccination files so far?

What is the status of updating your system?

What is your development status, production readiness date, etc?

DaVita

• They are most of the way through requirements
• Design is in progress; should be done mid to late next week
• Nathan feels DaVita is on track pending the question/scenario below
• Big question still working on is: How do we know what not to report?
  • If the expectation of managing other organizations records, they DaVita is not on track; if they do not have to do that, DaVita is on track
  • Clarified that Nathan is looking for scenarios between facilities or other facilities
  • Looking for business scenarios and expectations that the Program signs off on
  • For example, the scenario that as been raised is: the patient gets as flu vaccine at FKC in October, they come to DaVita in January. What is the expectation there? Recording for this discussion:   6:48 - 51:04
    • Per Nathan the only answer given is don't submit duplicated data; don't two organizations tell EQRS the same thing
    • This is also the same scenario that RHA is running into.  The other scenarios have been pretty clear
  • Per Howard, the issue of how far to go back?
    • Per discussions with Howard and Yvette, there are no business rules that prevent EDIs from reporting
    • Need clarification
  • Per Howard, its unrealistic for CMS to expect that EDIs are not going to report duplicates
  • A lot of duplicates will be reported and CMS needs to figure out how to scrub that; it is not the job of the EDIs
  • Per Yvette - vaccinations is supposed to be event based
    • Will need CMS to say that the expectation if for EDIs to only report vaccines during the time the patient was at their facility
    • Regarding duplicates - the system will match on the vaccine and the date that the vaccine was administered.  So it won't create a duplicate in that sense
    • If it is reported on a different date, than previously reported, it will add that record
    • Howard recommends a discussion on having a date ranges instead of a specific date
  •  Lisa has already spoken to ISG about creating a report for vaccinations; start working on this report in PI19
  • Per Nathan, they need to know what the report will look like before they build it
  • Howard more concerned about the reporting of duplicates
  • Per Kathleen - duplicate data is what they are reporting now; its separated out by facility
    • As long as the patient is vaccinated
    • Suggest to move forward with how it is and see what happens; if needed discuss enhancements for the future
  • Per Yvette - asking for EQRS and EDIs to meet in the middle
    • There is plenty of data now in clinical, with this first rollout we're only going to migrate from the latest (there are future plans to migrate all later)
    • Once this is deployed to prod, whatever vaccinations the patient has, the EDIs submit that data until we can get to a place where all of the history data has been migrated and there is the ability for EDIs to see what the patient has
    • Take this all in steps
    • It is not intended for the EDIs to have to log into the UI to get this data
    • This is a future thing that still has to be worked out - EDIs will have the ability, whether it is a physical report were it can be printed out or some other way to be able to see what information the patient has
    • Yvette is requesting to move forward that from the moment that vaccination data is in production, when the patient gets vaccinated the EDI will report it
    • Reporting will be event based; report after vaccinations went live
  • Definition for event based submissions Recording for this discussion:  30:09 - 51:04
    • Vaccination Data Submission Requirements and F&Q.pdf
    • Howard ask for EQRS to write a specific example on the timeliness issue and put that in the documentation where is says Timeframe for Data Submission

FKC

• Question from Kathleen - Does the migration also include the latest declination for the latest the patient did not receive it or are we only migrating patient received statuses?
  • Per Yvette we are only migrating the latest record or whatever is in clinical
• Question - In one of the "not received" instances for HEP B, one of the reasons in the drop down for not receiving it is "Series complete for antibody test"
  • There is no documented result limit on what indicates immunity.  There is no requirement documented on what the test score is and  when a patient is immune
  • Lisa will look that up

DCI

RHA

• Request from Howard - Have a discussion about timing of all this, testing sign offs, go live dates and so forth
  • This is a substantial development for the EMR vendors
  • No exact date but Howard is thinking July when they will have enough code written to begin some testing
  • A table has been created in the meeting minutes (below) on timing of the events