Blog from August, 2019

Report from the ONC Interoperability Forum demo:

• Demo went very well, we got postivie feedback
• Dr. Terry O'Malley: "You guys rock!"
• Many thanks to Dr. Miller and Brett Andriesen for organizing the demo, and to the team from eClinicalWorks, Epic, Medallies, Netsmart, and Qvera for the hard work.
• We made it to Twitter:
   

  Error rendering macro 'widget'

  com.atlassian.confluence.api.service.exceptions.IllegalURLException: The provided url- https://api.twitter.com/1/statuses/oembed.json?id=1164243552722927616&omit_script=true&lang=en is not included in the whitelist!.Please add the url to whitelist to allow access

Review of outstanding work, and a discussion on related items that can make the LTAC/SNF specification better:

• Possible future enhancement would be to add a reminder message from the SNF to the hosptial to have the patient properly prepped.
• Maybe we can work with quality measuremnts to reflect the timeliness and completeness of information exchange, and reflect patient satisfaction.
• The US CDI had a lot of coverage at the ONC Interoperability Forum, and they are planning an update mechanism, where more data classes and element will be added over time. If there is a way to have context-specific core data, that will be a great opportunity to add LTAC/SNF transfer information to US CDI in the future.
• Before we can make suggestions for additions to USCDI, we need to determine the gap between the mandated assessment data that the SNFs need (i.e. the Data Element Library), and what is sent by the hospital. A possible path forward may be:
  • Survey existing discharge summaries to see if nurisng assessments are already part of the data
  • Find out what nursing assessment data is in the various EHRs by the time the patient is transferred to SNF
  • Compare the above information to the data grid that we reviewed, possibly provide a crosswalk between hospital nursing assessements and SNF assessments
  • Use the existing hospital data as a beaseline to introduce quality measures for timeliness and completeness of data (Terry O'Malley to reach out to Beth Connor in CMS)
  • Start a process of improvement in order to get the appropriate data to the SNF

The ONC Interoperability Standards Advisory is taking comments for the next publication of the list. Currently, 360X is under Section II, Summary Care Record, Support a Transition of Care or Referral to Another Health Care Provider. We would like to give more visibility both to the 360X for Clinical Consultation Referral guide, and to the new in-progress 360X for transitions to SNF guide. Over the next couple of meeting we will develop a comment in that regard to be submitted to the ONC before the deadline on September 23.

Call was cancelled due to preparation for the ONC Interoperability Forum demo.

Short call, reviewed the SNF transfer transactions as discussed in the last call. Update on the demo preparation for the ONC Interoperability forum.

Reviewed discussions on Argonaut Scheduling and 360X. Both workflow alternatives have pros and cons. One of the options to add the referral information is to include a service request resource during the creation of the schedule.

Update on the demo preparations for the ONC interoperability Forum.