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

Openemr work on 4958 amc patient electronic access #4997

Merged

Conversation

adunsulag
Copy link
Member

This almost fully implements #4958. We still need to handle the group method calculations which will be done in a follow up PR.

This PR adds the 2015 AMC database fields to support 2015 rulesets. Instead of adding a bunch more branch conditions which complicates the code I abstracted the certification report types into its own class that contains the amc rule set type constants as well as data titles etc.

Implemented the AMC Patient Access (Required Test 2c) here.

I added in n the FHIR 3rd party api access instructions everywhere in the portal where accounts are created / credentials generated to give patients access and instructions on how to access their 3rd party apps. I also moved the FHIR server address URL into its own class so we can reference it in one place and throughout the codebase as well as in the email twigs.

I've also gone ahead and created twig email templates so that module writers and others can overwrite the message emails if they so desire.

I updated some of the FHIR Readme api documentation for 3rd party apps.

Added the 2015 AMC database fields to support 2015 rulesets.  Instead of
adding a bunch more branch conditions which complicates the code I
abstracted the certification report types into its own class that
contains the amc rule set type constants.
On the patient dashboard it was breaking due to missing the default amc
piece.
Added in the classes and database properties for Required Test 2c.
Saw we were copying the fhir address url all over the place so I put it
into its own constant.
Refactored the create credentials page to include the link to the FHIR
api and the fhir requirements doc.  I point the requirements doc
currently to our FHIR readme page but we may need this to be a dedicated
pdf or text document.  As part of this refactor I changed the templates
to be twig files.  Better separation of concerns and module writers can
now override the template.

Changed the size of the credentials popup to be a bit bigger to show the
larger amount of information we are displaying.
Missed the template twigs for the portal credentials refactor.
So there is some additional work we'll need to do with the AMC rule
calculations for group methods but this commit adds in the FHIR 3rd
party api access instructions everywhere in the portal where accounts
are created / credentials generated to give patients access and
instructions on how to access their 3rd party apps.

I've also gone ahead and created twig email templates so that module
writers and others can overwrite the message emails if they so desire.

I added the Clinical Rule text descriptions to the AMC rules for the
patient access.  I also centralized the AMC titles/code data arrays into
the CertificationReportTypes class.
@bradymiller
Copy link
Member

very cool stuff! even have twig for @robertdown 🎁
review complete (didn't test)

2DV-2

@adunsulag
Copy link
Member Author

@bradymiller @stephenwaite I believe I fixed all these issues. I'll move onto the other required test which should go pretty quick. We do need to figure out the grouping mechanism and hopefully we can discuss that on today's call.

@sjpadgett
Copy link
Member

thanks @adunsulag for another great project. You're promoted to Senior Administrator now, get to work!:)

@adunsulag
Copy link
Member Author

Lol, @sjpadgett I guess that makes you Senior Vice President Administrator.

@sjpadgett
Copy link
Member

I no longer work for titles @adunsulag. Atta Boys are my new fee schedule!

@adunsulag adunsulag deleted the openemr-fix-4959-amc-pi-hie-1 branch March 14, 2022 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants