Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weno follow up #7196

Merged
merged 5 commits into from
Jan 29, 2024
Merged

Weno follow up #7196

merged 5 commits into from
Jan 29, 2024

Conversation

sjpadgett
Copy link
Sponsor Member

  • correct interval for WenoExchange
  • add after actions to enable, disable and delete background tasks.

Fixes #

Short description of what this resolves:

Changes proposed in this pull request:

- correct interval for WenoExchange
- add after actions to enable, disable and delete background tasks.
@sjpadgett
Copy link
Sponsor Member Author

@dataengr More changes you may want to note.
@juggernautsei If interested in clean up pattern.
@bradymiller Unsure how you want to review but anything you note, say in merged original, I'll fix here. thanks!

…_followup

* 'master' of https://github.com/openemr/openemr:
  fix: support multiple modifiers in fee sheet (openemr#7166)
  feat: use global default visit category for add edit event (openemr#7190)
- find and populate user id to prescription table.
- remove encounter dependency to render weno prescription frame.
- add docblocks
- restore README module install instruction.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see that you dropped this file in the root of the module. I have read the entire file. I understand most of what it is doing. Is the pattern for the future of module building?

Copy link
Sponsor Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

only if needed to do specific module manager actions like remove a global when module is disabled etc.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, for my first use of this feature, I will be adding it to the quest lab module.
https://github.com/juggernautseinc/oe-quest-lab-hub
It has pieces that would need to be removed from background services and global.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do I get a module code review? @bradymiller

- remove encounter requirement my call
- fix user specific password get
- remove weno from custom menu.
@@ -12,6 +12,7 @@
use OpenEMR\Modules\WenoModule\Services\WenoPharmaciesJson;

if (isset($_GET['key']) && !empty(isset($_GET['key']))) {
// called from old v6.0.0 requirement.
Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think what Brady was getting at is that the script can't be left without any protection like if running from cli?

Copy link
Sponsor Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think so and is fine

Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but anyone could hit this file with a get request key param and start weno?

@sjpadgett
Copy link
Sponsor Member Author

Merging soon. If anyone has any further issue then by all means be my guess and change. @dataengr

  • Recommend you test for QA especially the pharmacy and prescription background tasks weno requirements for updates.
  • If specific user doesn't have credentials then weno widget shouldn't show.
  • Cleanup DB from v6.0.0 weno background tasks i.e remove. Actually I think i'll go ahead and do before merge so not forgotten.
  • If any reporting requires encounter then follow up. I don't see any and Sherwin added as openemr requirement and not weno.

- remove tasking call for old background tasks.
@sjpadgett
Copy link
Sponsor Member Author

okay @dataengr Removed what I think is old left behinds for old weno feature and I see no usage by module but correct me if im wrong.

$logsync = new LogProperties();
$logsync->logSync();
}

function downloadWenoPharmacy()
Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

southpark_cheering

Copy link
Sponsor Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fare thee well start_weno() :)

@dataengr
Copy link
Contributor

@sjpadgett, the method start_weno is no longer in use.

@sjpadgett
Copy link
Sponsor Member Author

it was a function and I removed it

@sjpadgett
Copy link
Sponsor Member Author

I think I did pretty good to make this module whole and clean. I'm sending back to @omegasystemsgroup to follow up with testing and any bug fixes I caused by making whole for openemr or otherwise missed in my testing which I wasn't charged with.
Merging and good luck Weno!

@sjpadgett sjpadgett merged commit 501cfa7 into openemr:master Jan 29, 2024
24 checks passed
@sjpadgett sjpadgett deleted the weno_followup branch January 29, 2024 16:50
@bradymiller
Copy link
Sponsor Member

2DV-2

sjpadgett added a commit to sjpadgett/openemr that referenced this pull request Feb 22, 2024
sjpadgett added a commit that referenced this pull request Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants