search

MeasureAuthoringTool / VSAC-Groovy-Framework

New repo for MAT framework for VSAC using Groovy.
Creative Commons Zero v1.0 Universal
0 stars 0 forks source link

Looking for assistance on building this project into the jar file #4

Open rsoltoff opened 3 years ago

rsoltoff commented 3 years ago

@cday-semanticbits My company (Medicomp Systems, Inc) has been using a fork of the MAT 4.6 internally for developing QDM measures for the quality payment program. I have been updating our version for the new VSAC apikey authorization. MAT uses this framework for the lower-level access to VSAC. I use eclipse 4.5.2 for the MAT fork development. So I imported this project into my workspace, installed groovy, and the groovy eclipse plugin. But there seems to be no info on what else is needed to build this project into the jar file used in MAT. Any assistance would be welcome. My email is rsoltoff@medicomp.com

Please disregard this issue. I finally found that to build the project, I had to specify in the project properties for the ANT Builder, that in the JRE tab, I had to specify the option, "Separate JRE" for the Runtime JRE. The project build now builds successfully. I am leaving this info here in case anyone else needs to know this.

cday-semanticbits commented 3 years ago

@rsoltoff Sorry I didn’t respond sooner I have been on leave for a couple of weeks. We are currently in the process of rewriting the vsac api to use the api-key and modernizing it. We are not going to use groovy. We have a release date of October 20th to get this in but we might implement it sooner. If you have time to wait that is probably the best approach.

However, if you need it now you can just overwrite the jar created from the build into lib/mat/vsac/1.0/vsac-1.0.jar in MAT:

And then run install-deps.sh from MAT. This basically adds it to your local maven repository manually.

-Carson

On Sep 21, 2020, at 1:49 PM, rsoltoff notifications@github.com wrote:

@cday-semanticbits My company (Medicomp Systems, Inc) has been using a fork of the MAT 4.6 internally for developing QDM measures for the quality payment program. I have been updating our version for the new VSAC apikey authorization. MAT uses this framework for the lower-level access to VSAC. I use eclipse 4.5.2 for the MAT fork development. So I imported this project into my workspace, installed groovy, and the groovy eclipse plugin. But there seems to be no info on what else is needed to build this project into the jar file used in MAT. Any assistance would be welcome. My email is rsoltoff@medicomp.com

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

rsoltoff commented 3 years ago

Carson, Thanks for the response. I did get it working. As I noted, we are still using MAT4pt6 for inhouse development. We have made some changes to that for a few QDM items that were added since 4.6. We run the MAT from an eclipse run configuration because I have never been able to get the war running asa a web site under glassfish. Although clumsy, it suffices our needs.

            I did manage to get all the groovy stuff added in for eclipse and was able to compile that vsacGroovy project to a jar file. I since revised the MAT client and server pieces to accept either the login and password or just the apikey. And I modified the groovy class accordingly. It all works fine for us.

            After the 1st of next year when the apikey will be the only way to access the vsac, I’ll probably just remove the login/password stuff for vsac. Since this is just used internally, I am thinking of adding the apikey to the user table in the database and doing a retrieve of it when needed. Can’t stand having to copy and paste that long apikey in when needed. There are three of us that work with our local version of the MAT.

            For reference, I am not a big Java developer, but have been able to learn more with the MAT source. Our company, Medicomp Systems, Inc., used the MAT for about 5 years to create artifact files for all of the QPP measures. We have a QDM execution engine in our SDK that can evaluate any measure: CQM or QPP. Since we have yet built a CQL (ELF) execution engine, we still rely on the QDM artifacts. As such, we also maintain MAT 4pt6 generated versions of the eCQMs which we have to then maintain. Perhaps one day we will build a CQL execution engine.

From: Carson Day notifications@github.com Sent: Friday, October 2, 2020 11:49 AM To: MeasureAuthoringTool/VSAC-Groovy-Framework VSAC-Groovy-Framework@noreply.github.com Cc: Roy Soltoff rsoltoff@medicomp.com; Mention mention@noreply.github.com Subject: Re: [MeasureAuthoringTool/VSAC-Groovy-Framework] Looking for assistance on building this project into the jar file (#4)

@rsoltoff Sorry I didn’t respond sooner I have been on leave for a couple of weeks. We are currently in the process of rewriting the vsac api to use the api-key and modernizing it. We are not going to use groovy. We have a release date of October 20th to get this in but we might implement it sooner. If you have time to wait that is probably the best approach.

However, if you need it now you can just overwrite the jar created from the build into lib/mat/vsac/1.0/vsac-1.0.jar in MAT:

And then run install-deps.sh from MAT. This basically adds it to your local maven repository manually.

-Carson

On Sep 21, 2020, at 1:49 PM, rsoltoff notifications@github.com<mailto:notifications@github.com> wrote:

@cday-semanticbits My company (Medicomp Systems, Inc) has been using a fork of the MAT 4.6 internally for developing QDM measures for the quality payment program. I have been updating our version for the new VSAC apikey authorization. MAT uses this framework for the lower-level access to VSAC. I use eclipse 4.5.2 for the MAT fork development. So I imported this project into my workspace, installed groovy, and the groovy eclipse plugin. But there seems to be no info on what else is needed to build this project into the jar file used in MAT. Any assistance would be welcome. My email is rsoltoff@medicomp.commailto:rsoltoff@medicomp.com

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/MeasureAuthoringTool/VSAC-Groovy-Framework/issues/4#issuecomment-702810762, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALUANCVD33HO2UCGKFJVKDDSIXY7NANCNFSM4RSNO3RA.

cday-semanticbits commented 3 years ago

Glad you were able to get it working … it is always interesting to see how people are using MAT. We are trying to improve so it is easy for others to use via open source, but unfortunately that is only available in the latest versions.

-Carson

On Oct 2, 2020, at 12:03 PM, rsoltoff notifications@github.com wrote:

Carson, Thanks for the response. I did get it working. As I noted, we are still using MAT4pt6 for inhouse development. We have made some changes to that for a few QDM items that were added since 4.6. We run the MAT from an eclipse run configuration because I have never been able to get the war running asa a web site under glassfish. Although clumsy, it suffices our needs.

I did manage to get all the groovy stuff added in for eclipse and was able to compile that vsacGroovy project to a jar file. I since revised the MAT client and server pieces to accept either the login and password or just the apikey. And I modified the groovy class accordingly. It all works fine for us.

After the 1st of next year when the apikey will be the only way to access the vsac, I’ll probably just remove the login/password stuff for vsac. Since this is just used internally, I am thinking of adding the apikey to the user table in the database and doing a retrieve of it when needed. Can’t stand having to copy and paste that long apikey in when needed. There are three of us that work with our local version of the MAT.

For reference, I am not a big Java developer, but have been able to learn more with the MAT source. Our company, Medicomp Systems, Inc., used the MAT for about 5 years to create artifact files for all of the QPP measures. We have a QDM execution engine in our SDK that can evaluate any measure: CQM or QPP. Since we have yet built a CQL (ELF) execution engine, we still rely on the QDM artifacts. As such, we also maintain MAT 4pt6 generated versions of the eCQMs which we have to then maintain. Perhaps one day we will build a CQL execution engine.

From: Carson Day notifications@github.com Sent: Friday, October 2, 2020 11:49 AM To: MeasureAuthoringTool/VSAC-Groovy-Framework VSAC-Groovy-Framework@noreply.github.com Cc: Roy Soltoff rsoltoff@medicomp.com; Mention mention@noreply.github.com Subject: Re: [MeasureAuthoringTool/VSAC-Groovy-Framework] Looking for assistance on building this project into the jar file (#4)

@rsoltoff Sorry I didn’t respond sooner I have been on leave for a couple of weeks. We are currently in the process of rewriting the vsac api to use the api-key and modernizing it. We are not going to use groovy. We have a release date of October 20th to get this in but we might implement it sooner. If you have time to wait that is probably the best approach.

However, if you need it now you can just overwrite the jar created from the build into lib/mat/vsac/1.0/vsac-1.0.jar in MAT:

And then run install-deps.sh from MAT. This basically adds it to your local maven repository manually.

-Carson

On Sep 21, 2020, at 1:49 PM, rsoltoff notifications@github.com<mailto:notifications@github.com> wrote:

@cday-semanticbits My company (Medicomp Systems, Inc) has been using a fork of the MAT 4.6 internally for developing QDM measures for the quality payment program. I have been updating our version for the new VSAC apikey authorization. MAT uses this framework for the lower-level access to VSAC. I use eclipse 4.5.2 for the MAT fork development. So I imported this project into my workspace, installed groovy, and the groovy eclipse plugin. But there seems to be no info on what else is needed to build this project into the jar file used in MAT. Any assistance would be welcome. My email is rsoltoff@medicomp.commailto:rsoltoff@medicomp.com

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/MeasureAuthoringTool/VSAC-Groovy-Framework/issues/4#issuecomment-702810762, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALUANCVD33HO2UCGKFJVKDDSIXY7NANCNFSM4RSNO3RA. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/MeasureAuthoringTool/VSAC-Groovy-Framework/issues/4#issuecomment-702818499, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANKCAJPFJGDY4VLZGLJFSBTSIX2V7ANCNFSM4RSNO3RA.