You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

Date

Attendees

Name
Adrienne Adkins
Adrienne Ray

Ahmar Wazir


Anitha Chintalapatix
Arnie Esparterox
Branon Barrettx
Cheri Jergerx
Chris Brownx
Deb Wilsonx
Dianna Christensen
Hari Krishna
Heather Moore
Howard Thomasx
Janet Hutchinsonx
Jason Clem
Jennifer Bailey
Julie Alvarezx
Kathleen Prewittx
Kelly Llewellynx
Lakshmi Eriginenix
Leah Skien
Lisa Rees
Melissa Fieldhousex
Michael Kennedyx
Nathan Muzosx
Pandu Muddana
Preston Brownx
Revathy Ramakrishnax
Scott Laughlinx
Sarah Fillingx
Seema Sreenivas
Steve Goodmanx
Vladimir Ladikx
Yvette Brown
Zac Cohen
Zachary Serleth




Agenda

ItemsWho
Meeting RecordingArnie

This session will be recorded for the purpose of documenting the meeting minutes and action items. If there are any objections to the recording of this session, please make it known now. Absence of an objection to the meeting being recorded will count as consent to recording this meeting.

https://zoom.us/rec/share/Hz2Qt2NnAWjSJ8FMKLJPIEDUpzYIzl8t-XOWWzE4D_2VXP-mkczIzBSQPhPMne2f.ymyTmhIy-AGbM9Jc Passcode: zhv.BZ8C 

Action Items follow upAnitha/Scott
  • If they were to report "other" as a race, would they not be required to report country of origin or tribe? Do we have to submit a tribe and country?
    • Country of origin and Tribe fields are not required for Race type Other.
  • Chris Brown asked if there is a place on confluence that tracks when things (updates/deployments) go live (for example, a feature page that shows date when something goes live)?
    • Resources and References - EQRS Communications Hub - HCQIS Confluence (cms.gov)
    • Added two new columns to the feature page table - Prod Preview Date and Prod Date
    • From a workflow perspective, typically a release will follow from Prod Preview to Prod, sometimes same day or one day after
    • Request from Chris - display/capture EQRS rule updates or "hot-fix"/non major release dates that can be shared with the EDI Submitters that may impact their ability to correct/update patient data
      • Scott will research a way to be able to identify a feature that a rule update or "hot-fix" impacts, so the EDI Submitters are aware of the change (action item)
      • Chris is "following"/"watching" the release checklist area which seems to help identify the "hot-fixes" and changes
    • Goal of CMS ADO is to be able to share with the EDI Submitters as soon as possible files that they are highly confident will make it into prod
    • This will give the EDIs ample time to align and plan their development of that file, etc
  • Confirm the schema/feature release is available in prod preview for testing. It would be helpful to know when something is available for testing and when it has gone to Prod or when they can expect to go to Prod
Test and Feedback Files (XSD, XML, Data Dictionary Updates)Anitha

Nursing Home  - The sample xml file (eqrs_nursingHome_True_Permanent_Resident_testfile.xml ) for Nursing home has been updated with the correct elements.

  • Per Kelly Llewellyn (NRAA), they are aware of the updated XML and their vendor are thrilled
EDI Submitter's Progress (upcoming feature development)EDIs

DaVita

  • Nathan was following up on the ability to "follow" the EDI Confluence pages
    • Per Melissa Fieldhouse. there is no update at this time but she will follow up with Atlassian (action item)
  • Thank you to the team for all their hard work in resolving the timeout issue
  • Nathan was following up with the topic - Effective date logic that the effective date is auto populated with current date if they do not send one
    • Scott did brief Lisa and Ahmar and at this time no updates to share
    • Nathan (DaVita) would like to keep on the radar; definitely one of the top 10 on their list that is impactful

FKC

  • Thank you to the team for resolving the timeout issue
  • FKC still seeing the 20016 error code - multiple patients mapped to org ID
    • Currently triggering with the 401 errors
    • Per Nathan, DaVita is seeing the error as well
    • Per Michael, he is researching; he thought the fixes to the 20016 and 401 errors were already deployed to prod
    • Per Lakshmi, the fix was promoted on 11/9
    • Per Revathy it may be a timing out issue b/c 11/9 is when they start encountering the gateway issues
    • FKC will continue to resubmit their submission files and see if the error is still coming up

DCI

  • They tried to submit small clinical and patient files today (12/3) and they failed; they reported to the helpdesk today
  • It may be a credentialing issue
  • They were successful with submitting files Tuesday and Wednesday
  • Lakshmi will check if the credentials for DCI have expired or need to be renewed
    • Per Preston, the DCI credentials are expired in production
    • How can Vlad/DCI know when their credentials are expiring?
      • The expiration of credentials is a security policy
      • They are notified to the email on file
      • Vlad will send Lakshmi the 2 email addresses the email notifications should go to

NRAA

  • Per Howard - Since the EDIs will be closing out submissions in February 2022, suggestion to have an agenda item added for future meetings to go through the clinical comply completion for each of the EDIs and see where we are at as a community
    • Scott will talk to Lisa about getting some similar reporting that we had for the 2020 period such as the reports that Diana provided showing the quantity of submissions pending for independent facilities as well as the EDIs
    • Nathan also suggest that we perform an "error analysis" as well to determine the main errors that everyone is encountering and what is triggering these errors
      • Per Scott - CMS does have a feature in their backlog that will provide error reporting; this may be pulled through the UI
      • Per Michael - Nathan may be suggesting a manual report that can be run when they have a meeting with the whole group as the submission 2022 comes to a close.  Michael said he will try to work on it
  • Per Howard -  Where are we at with the whole Depression and Mental Health screening?
    • Per Scott - From an ISG perspective, they reviewed the current functionality at the last system demo (recording can be found on the public page)
    • The system has been built based on the requirements provided by the program
    • Feedback from the system demo has been captured and documented, the feedback will be passed on to the program
GeneralScott
  • The public EDI website (confluence page) has been redesigned for better organization and access to EDI documentation/information.  Link below:
  • REMINDER: For any issues encountered, send an email to the help desk using the following email address:  qnetsupport-esrd@hcqis.org with URGENT in front of subject line for urgent matters
    • Scott will be working with Shamim to enhance the support process that the EDIs follow with CMS
    • The help desk has some future enhancements coming for Service Now that will help us 
  • Question from Nathan - With the turn of year, it's also time for annual attestations
    • As part of the process the EDIs usually get a weekly report of the status of the ICHCAPS attestations
    • This report has come from different contracting groups
    • Per Janet Lea Hutchinson - this is not something the NCC has provided
    • Per Scott - we will need to get back to Nathan on this (action item)

Action Items:

  • Request from Chris - display/capture EQRS rule updates or "hot-fix"/non major release dates that can be shared with the EDI Submitters that may impact their ability to correct/update patient data
    • Scott will research a way to be able to identify a feature that a rule update or "hot-fix" impacts, so the EDI Submitters are aware of the change Scott Laughlin
  • Nathan was following up on the ability to "follow" the EDI Confluence pages
    • Per Melissa Fieldhouse. there is no update at this time but she will follow up with Atlassian Melissa Fieldhouse
  • Question from Nathan - With the turn of year, it's also time for annual attestations
    • As part of the process the EDIs usually get a weekly report of the status of the ICHCAPS attestations
    • This report has come from different contracting groups
    • Per Janet Lea Hutchinson - this is not something the NCC has provided
    • Per Scott - we will need to get back to Nathan on this Scott Laughlin
  • If they were to report "other" as a race, would they not be required to report country of origin or tribe? Do we have to submit a tribe and country, or we don't have to?
  • Chris Brown asked if there is a place on confluence that tracks when things (updates/deployments) go live (for example, a feature page that shows date when something goes live)?
    • Per Scott, we don't track it today but if that will help the group, it will be discussed on the CMS side Scott Laughlin 
  • Confirm the schema/feature release is available in prod preview for testing. It would be helpful to know when something is available for testing and when it has gone to Prod or when they can expect to go to Prod Anitha Chintalapati
  • Request from Yvette to Nathan and Vlad to send an email to Lisa with what the proper wording should be for the questions they brought attention to in the meeting.  It will need to be approved by the program before Yvette can make any changes to the verbiage (Nathan and Vlad)
  • Scott will discuss revisiting the DaVita effective date and date of death issue with Lisa Scott Laughlin 



  • No labels