Hello,
When editing the insurance within the patient’s dashboard, the required Selected Policy auto populates insurance information from a dropdown list that is most often incorrect. This makes it difficult to review a patient’s insurance information if subtle correction is needed. Any idea of how to fix this undesired outcome?
Hello @sophisticated_acquis
Can you give details of how the autopopulated info is incorrect?
What info is in there, where does it come from, what should be there?
A screenshot would be helpful.
- Harley
Basically, the Selected Policy is a required span element that presents a drop down of various policies that have been saved at some point. This creates a long list of insurance policies with various identifiers. When edit insurance is selected the dropdown defaults to the first item (usually) contained within the dropdown menu. This changes whatever default values for insurance information that was stored there prior to you clicking on the various fields to edit. I do not know how to resolve this issue. I would state that it would probably make sense for the default value stored within this dropdown to be the current information stored for the current patient’s policy rather than some random subscriber’s information and policy. I don’t know if that means making Selected Policy not required or if that means defaulting it to the last known policy information stored within the chart.
Hi @sophisticated_acquis
That’s much better, gives others who know more about this than I do something to work with.
I’m no dev but it sounds like what you are seeing is your browser autofilling previously entered information, don’t you think? Does OpenEMR have any control over that? I mean, when I use different browsers on the same site-- or the same OpenEMR instance- different stuff gets auto-populated in the text areas and dropdowns. That tells me it’s not the EMR, but the application that is presenting it. But I could be wrong about that.
As far as changing an insurance datum from required to not, that can result in a lot of extra work tracking bad claim submissions if people do not enter it even a low percentage of the time.
Best- Harley
The site did not autofill data until the Selected Policy drop down was created and made to be a required element. I indicated it with arrows. it is reflected within this code from a twig file below this paragraph. If that drop down had a current policy option that it defaulted the pid of the patient within the insurance_data table, I think it would not spit out the last saved policy used period, but default to what was last saved within that chart. Cutting off autofill did not resolve this issue.
<div class="col-md-6">
<div class="form-row insurance-type-selector-row-{{ instype|attr }}">
<div class="col-md-3 label_custom pb-3">
<span class='required'>{{ "Selected Policy"|xlt }}</span>
</div>
<div class="col-md-9">
<select id="insurance-type-{{ instype|attr }}" class="form-control form-control-sm sel2 mb-1" data-type="{{ instype|attr }}" class="d-none">
</select>
</div>
I understand about cutting off a browser autofill, but the Selected Policy dropdown defaults to the first item in the drop down which triggers all the data to be changed. I have been looking to see how it is referencing and it is consistently populating the first option in the dropdown. I assume if there was a default selection in the drop down it could be directed to retrieve the information stored from the previous save.
Hi @sophisticated_acquis
Well, I’m glad we’ve gotten to this level of detail in the descriptions, it should help any of the devs reading this to make an informed reply to your question! As I’ve mentioned, I am not a dev and this has gone far beyond my user- oriented expertise.
Much luck- Harley
hi @sophisticated_acquis and @htuck , the insurances have had a major upgrade and we can now store a history of policies. In order to manage them properly you can create new policies and use the effective date end to retire a prior policy. The effective date will load the most current policy if you don’t.
@stephenwaite, when you go to edit a policy, the policy was not defaulting to the policy information of the currently loaded chart. That is the information is set to the first item on the drop down menu, which could be from a different chart. Is this your experience or anyone with a number of patients?
By the way the effective date & subscriber date of birth is expected to be entered with dd/mm/yyyy instead of the typical mm/dd/yyyy date convention that is typically the default.
Updated to the Patch 2 and both the date issues and the Selected Policy problem were fixed. Thanks.
1 Like