Understanding Welkin <> Programmer

Here are some important things to know about the Welkin <> Programmer Integration:

• A Baseline Visit consists of:
  • 1. Baseline Assessment
  • 2. Pain Map
  • These items can be authored either in Programmer or in Welkin. Once a Pain Map exists in Welkin, however, the pain regions for a patient can only be modified from Programmer.
• Welkin syncs with Programmer once a day, at approximately 2am PT.

FAQ:

Help! The Baseline Assessment for my patient says Jan 1, 2009

This is because Welkin received no baseline date input from Programmer. Jan 1, 2009 is the default date that we set if no date is available. To fix this, you should edit the date of your Baseline Assessment from Programmer, and the correct date should be reflected in Welkin upon the next sync.

Help! The Baseline Pain Map for my patient has no pain regions

This is because Welkin received no baseline pain region input from Programmer. You can revisit Programmer to amend the patient's pain regions. The corrected pain regions should be reflected in Welkin upon the next sync.

Why is there an empty Baseline Assessment on my patient's timeline?

Every day, Welkin detects patients that have a Pain Map but no corresponding Baseline Assessment. If no Baseline Assessment exists, we insert an empty Baseline Assessment on the patient’s timeline, which the coach can complete at their convenience.