33 results found
-
Play an audible prompt when a new basket is added to QUEUE
If I've finished dispensing all baskets in the Queue and a new one shows up it would be useful to hear a sound indicating this as I'm not always monitoring the Queue
13 votesWe have released a new Notification function for MedView Flow.
This new function will email the account of your choice when a script arrives into your MedView Flow Queue from an external source.
For more information on this new feature see here: http://webhelp.medview.com.au/pharmacy/help-topics/flow-notify-pharmacy.htm
We hope this new feature will prompt the pharmacies that there is something new in the queue to be actioned.
-
Printing paper token on supplied A5 repeat paper
Ability to print paper token on PBS supplied A5 repeat paper. Would allow for better work flow and uniformity for patients that want paper tokens
12 votesThis functionality has been added to Fred Dispense Plus and Fred Dispense Classic
-
dispense
need to press F12 before click on the dispense in medflow, would be better if it clears up the window and go straight to load the script for dispense without having the need to press F12 all the time.
12 votesFeedback has been passed onto the Fred Dispense team
-
Configurable option to print out the virtual script image
Ability to print out the Virtual Script image for an electronic script to be kept on file for these reasons:
- DDs are required to be kept on file
- Collating numbers for claim - establish if the script is electronic or missing
- Patient finds an issue with the dispensed scriptWould be useful to be able to print out the image before the basket moves to the next column
12 votesThanks for this idea,
We’ve reviewed this and believe printing the virtual script image is not required for the following reasons:
- DDs – this information is in the Dispense regulatory report
- Collating numbers for claim – this is available in the Dispense claiming report which shows whether the script is an eScript
- Patient finds an issue with the dispensed script – you can print copy of the token can be produced as evidence to show to the patient
-
Importing patient details
When Medview flow imports script data into FRED, it should also import the date of birth, address, phone number, email as these details are available on the escript already and are required to dispense the escript, it is just an extra step to have to input them manually.
8 votesFeedback has been passed onto the Fred Dispense team.
-
7 votes
Feedback has been passed onto the Fred Dispense team
-
Dispense label for e-scripts should only be the actual label that goes on the box and not the other smaller stickers.
As there are no paper script or duplicate script to be labelled, the additional smaller labels are not required, so FRED shouldn't print on them.
6 votesFeedback has been passed onto the Fred Dispense team
-
Adapt the print processes within Flow to use A5 repeat forms for eScript printouts.
Using A4 paper is forcing pharmacists to use paper that they will have to supply [ie pay for]. This must be going to save the PBS/Medicare millions of dollars - there will be less repeat forms needed and less prescription forms needed. Maybe an increase in the dispensing fee is warranted or PBS can supply A4 paper as well as repeats forms!
6 votesFeedback has been passed onto the Fred Dispense team
-
Patient name needed in email header.
If we receive an eScript token by email, it is necessary to open the link, copy the token, open Flow and, finally, paste the token to find out who the patient is. It is not until then that we can make an informed decision what action to take. [eg dispense now, file for future use, wait until patient presents]. This adds significantly to the workload - we are essentially half-processing the script before we know whether that is appropriate. There must be a way to identify the patient earlier in the email process. Once in the "IN" area of Medview…
6 votesHi Stephen, Regarding your point around identifying the Patient in the email heading for the token, we're unable to display their name due to ADHA's conformance points to not identify the Patient at that stage. In regards to the issues around half-processing scripts we believe the ASL will ease this problem. We're happy to take some further feedback from you if you'd like to reply to this comment
-
Screen resizing
Can there be more flexibility in the resizing of the screen in the browser? We'd like to shrink it down to fit 2 windows on a large screen and it's not workable.
6 votesHi Amanda, one of our consultants contacted you about this and zooming out using the browser settings has resolved this
-
Please consider printing on the labels of e-script items where the repeat has gone. Paper, SMS or emailed. Patients often don't know.
I understand that space on the labels is tight, but having it printed on the label where the repeat has been issued to will help patients locate their future tokens.
5 votesFeedback has been passed onto the Fred Dispense team
-
eRX Token "Print" - print format should be a5 format
Print format for eTokens should be A5 as currently its orientation is not suitable for repeat folders and is awkward.
5 votesHas been transferred to the Fred Dispense Plus UserVoice forum
-
Put baskets in order of pick up priority
Prescriptions marked for future dispensing eg tomorrow, seem to still sit at the top of Queue,Checking and Out even if there are waiting scripts added to the queue. I thought that the system was designed to order by pick up priority. I think that it would be preferable for workflow to prioritise by pickup time.
5 votes -
ePrescription Indicator on Script Label
Request for an enhancement to Dispense Labels for ePrescriptions, to assist with checking when an ePrescription is dispensed for a patient who may also have paper prescriptions dispensed in the same batch of scripts, the Script Label will help the checking pharmacist know where to look to check that particular script, rather than looking for the paper script with the others
4 votesFeedback has been passed onto the Fred Dispense team
-
Indicator that token has been used
HI
I’m writing to you with a suggestion regarding e-script tokens on patient’s phones. Once a token has been used, would it be possible that if they try to reload it again from the text message that it would load with a different coloured background, and some words to say it has already been used. It would help avoid a lot of wasted time in the pharmacy.Regards,
Brian2 votesHi Brian, If the script is in any state other than active, the QR code is hidden and we display a message to indicate that it cannot be dispensed
-
eSCRIPTS emailed direct from GP have NO identifier patient or clinic. It looks like junk email
The e script exchange emailed scripts are impossible to find. They look like junk mail. Have logged calls re this and no solution yet. When you try to search your email account there is no identifier for the GP clinic who sent them and you cannot search by patient name. Emails come through as noreply@emailprescription.com.au and only identifier is patient initials and drug. Impossible to find when a patient presents telling you their script is emailed from their clinic.
2 votesHi Jo, the content of the token for both SMS and Email is governed by ADHA and produced on behalf of the Department of Health. Therefore the content is defined and we cannot change it
-
2 votes
Thanks for the feedback, this function is controlled within Dispense. We will pass this feedback on to our Dispense teams
-
patient history highlight e for escript
When looking at Patient history in F2 in Fred dispense, can the escript be highlighted as the e is very small. Like owing and deferred scipts colours, very difficult to quickly scan for e.
2 votesThanks for the feedback, this function is controlled within Dispense. We will pass this feedback on to our Dispense teams
-
2 votes
Hi We've since had some feedback from the Dispense teams about displaying the first initial and the surname. This was a conformance requirement from the Department of Health around privacy which only allows us to print the Patient's Initial and Surname
-
Ability to Get Script back into 'Done' if accidentally removed
In the instance of a Script being successfully processed through Medview Flow, and on to Dispense, but is accidentally removed from MedView Flow - can't view the Script in "Done".
Can a feature be added to "re-send" a completed Script to Flow?2 votesThank you for your idea. This is not in our roadmap but our recommendation is to rescan the script into Flow if the basket has been removed to view the script again
- Don't see your idea?