Lock order of Medicare patient claim
D
Daniel Shea
When submitting patient claims for Medicare, it is currently possible (and too easy) to accidentally submit claims on unpaid invoices. When payment is processed before the Medicare claim, things work as intended. When the claim is accidentally submitted first, Medicare defaults to an extremely inconvenient and archaic process where it sends a paper cheque for the service provider TO THE CLIENT. This is surely never a desired default use case for the claiming feature. We suggest that Medicare patient claims be disabled by default on unpaid invoices.
This feature is potentially high-impact in terms of inconvenience and lost time. If Coreplus is not interested in offering this feature, then we would be interested in discussing the possibility of obtaining API access to have our own developer incorporate this functionality.
Log In
Lachlan Cox
Hi Daniel,
Thanks very much for your idea and feedback.
We agree that this would be a good addition to our patient claiming functionality.
In terms of expected behaviour, although it is an inconvenience to all parties and I agree with your position that almost all users would not want this outcome, it was a Medicare requirement that we have a channel to allow unpaid patient claims to be submitted, as part of our integration certification.
With that in mind, would a pop-up when the user clicks the save button that warns that no payment has been applied, and requires confirmation to proceed with sending the claim, be an acceptable solution?
D
Daniel Shea
Lachlan Cox: Hi Lachlan, given the requirements you mention, that would be an immensely helpful improvement!
What might the timeframe for this sort of change?
Lachlan Cox
Daniel Shea: Hi Daniel,
Very glad to hear that.
I have just created the ticket for this work, and have added it to our back log.
Although not a massive change, we need to prioritise this into our pipeline along with already planned works, so I think we may be able to address in early 2024.
I'll be sure to provide you with updates as they occur.
Thanks.
D
Daniel Shea
Lachlan Cox: Hi Lachlan (and team). I just wanted to check in on this, as we're in the thick of early 2024 now. Any updates?