|Deployment date:||Monday, November 11, 2019|
|Deployment window:||11AM - 2PM ET|
NOTABLE FEATURES IN THIS RELEASE:
✓ Created Provider user field uniformity across the Enterprise and Site portals
✓ Stroke: Weight value carries over from Vitals to Alteplase Decision forms and vice versa
✓ Stroke: Replace "tPA" with "Alteplase" in PDF/CCD reports
✓ Imaging improvements
In This Release
Created Provider user field uniformity across the Enterprise and Site portals
We have addressed a few discrepancies between the Provider user fields across the Clinical Site fields and Enterprise fields. We have:
- unified the order of the fields within the Site's 'General' tab and the Enterprise fields
- added missing fields on Sites and Enterprise
- First Name
- Last Name
- Cell phone
- SIP Address (Missing from Enterprise)
- Vidyo Address (Missing from Enterprise)
- Answering Service (Previously "Answering Machine")
- Office Phone
- Office back
- Group Pager
- Organization Name
- Zip/Postal Code
- National Provider ID
- DEA Number
- Medical License Number
- answering service (Answering Machine on sites)
- contact preference (Missing from sites)
- street 2 (Missing from sites)
Stroke: Weight value carries over from Vitals to Alteplase Decision forms and vice versa
In a scenario where both 'Vitals' form and 'Alteplase Decision' forms exist in a case, entering the patient's weight in one form will auto-populate the weight in the other form. Each time the weight value is changed, it will adjust accordingly in the other form as well, unless the other form is signed and locked. The dosage calculations will be recalculated as the weight value is adjusted.
If the weight is removed in one form, it will be removed in the other form also.
Stroke: Replace "tPA" with "Alteplase" in PDF/CCD reports
In a previous release, we replaced "tPA" with "Alteplase" across the web platform. In this release, we are including the "Alteplase" change to be reflected in PDF/CCD reports.
We’ve added additional configuration for when a new imaging study gets uploaded via an Ambra Gateway. In the instance of a time-sensitive stroke case, we can now safely enable this notification without the risk of duplicate patients or cases getting created.
New settings will now allow you to choose whether this study will trigger off a new patient to be created if a matching patient is not found. We have also added a setting to decide whether a new case should be created if one is not active for that patient.
By adding expanded configuration here, you can choose to only receive notification events for new studies if there is already a matching active case in American Well.