WWYD? HUB Accounts
A resident would like visibility to his attending’s cases to review the plan prior to the case and for research purposes. What do you do?
Create hospital staff account for the resident.
Documentation: Obtain written confirmation via email from surgeon stating they would like their resident to have visibility to all their cases. (Save in Salesforce)
Which of the following are we contractually safe to do Bi-Direction?
-Intelerad (Ambra & LifeImage)
-Powershare
-Medicom
-Change Healthcare
-VPN
- Powershare: PowerShare Accelerator needed & mapped to the HUB
- VPN: Site-Site VPN with push functionality needed
- Medicom: Mapped to HUB
Note: need proper configuration of PACS to accept and display UNiD Plan Memos.
What identifier do we use with Ambra to map images to the HUB?
AE Title
You have PACS log-in at the spine practice where most imaging is completed. 2 people have access on the team.
What would be an example to transition this optimal workflow to a favorable workflow?
- Q/R
- Auto Routing
- Add a DICOM export workflow mapped to hub allowing lab to self push to Search PACS
Note: you do not need to remove PACS access when favorable workflow is achieved.
An existing UNiD surgeon has a non UNiD surgeon serving as an assisting surgeon on a case. The non UNiD surgeon would like the ability to see the case on the HUB, but is hesitant about completing a LINK and doing the whole onboarding process. What options do you have?
Let the rep/surgeon know we don’t have the account type in the Hub to only provide visibility to one case so our options are…
Onboard non UNiD surgeon (complete LINK and collect preferences) and then make them co-surgeon on the case with the existing UNiD surgeon.
If the non UNiD surgeon does not want to complete onboarding:
Non UNiD surgeon can get a hospital staff account created but this would grant them access to all of the primary surgeons case, in which case we need written documentation from the primary surgeon confirming this visibility is ok.
Can we create bi-direction if the workflow is not through the hospital (example: private practice)
Workflow should be mapped to the contracted hospital
Within the context of PowerShare, why is a Send Channel important for mapping to the HUB? If an account is not willing to create a send channel, what is an alternative to accomplish the same goal?
Send Channels allow Medtronic to internally edit the institution name for mapping to the HUB. Alternatively, the account can choose to create a rule to edit the institution name themselves without creating a send channel.
You have EpicCare Link at the hospital with 4 surgeons added to surgeon daily. Several MDT users have access, but only 1 person consistently logs in.
What would be an example to transition this optimal workflow to a favorable workflow?
- SFTP/HL7
- FHIR
Note: You do not need to remove ECL access if favorable access is achieved.
At Hogwarts Hospital, Dr Dobby has his fellow approve his cases, however, these fellows do not operate independently. What do you do?
Create surgeon account for fellow to serve as delegate approver. Walk delegate approver through HUB and approval process/timeline/chat. CM to add fellow as co-surgeon on all of Dr Dobby’ cases
Documentation: Dr Dobby must confirm via email that he wants fellows to view and approve all cases. (Save to Salesforce)
How do configure the DICOM wrapped PDF to go to the correct patient in PACS
Pre-Op DICOM Accession Number
What is the difference between a Send-to Destination (DICOM Export) versus a Send Channel?
A Send Channel is specific to Nuance PowerShare and is the connection between Hospital PACS to Medtronic PowerShare.
A Send-to Destination is a DICOM Direct Send connection from Hospital PACS to Medtronic HUB (PACS to PACS).
This is standardly done when setting up a VPN Connection. This is an optional step when creating a 3rd party connection (i.e. PowerShare, Ambra, Medicom, LifeImage).
Within the context of PowerShare, an account can choose to leverage the send channel as a DICOM export, but it is not a mandatory configuration. In other words, an account can have a send channel without having a DICOM export.
You have VPN-Push workflow at the hospital and the turnaround time is < 8 business hours. They have denied any automation--despite using all the options in our toolbelt.
What would be an example to transition this target workflow to a favorable workflow?
- Bi-direction (OR-Memo to PACS)
- VPN to PowerShare or Medicom