-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feature/v 4 lib upgrade #140
Conversation
…PAIN-MANAGEMENT-SUMMARY into feature/v-4-lib-upgrade
…PAIN-MANAGEMENT-SUMMARY into feature/v-4-lib-upgrade
…PAIN-MANAGEMENT-SUMMARY into feature/v-4-lib-upgrade
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks also for adding and maintaining accurate test code!
README.md
Outdated
@@ -8,7 +8,7 @@ The Pain Management Summary SMART on FHIR application was developed to support t | |||
|
|||
The Pain Management Summary SMART on FHIR application was piloted during Summer 2018. Local modifications and development were needed to fully support this application in the pilot environment. For example, custom development was needed to expose pain assessments via the FHIR API. See the pilot reports for more information. | |||
|
|||
This application was originally piloted with support for FHIR DSTU2. The app has been updated since the pilot to also support FHIR R4, although pilot R4 support has not been piloted in a clinical setting. | |||
This application was originally piloted with support for FHIR DSTU2. The app has been updated since the pilot to also support FHIR R4, although pilot R4 support has not been piloted in a clinical setting. In addition, value sets and standardized codes have been updated since the pilot. See the comments in the bundled CQL for details. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this still true?
[...] although pilot R4 support has not been piloted in a clinical setting.
2. Select the ‘Generate new API Key’ checkbox | ||
3. Click ‘Save Profile’ | ||
4. Your new API key should now be listed. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice addition, thanks.
…om/uwcirg/AHRQ-CDS-Connect-PAIN-MANAGEMENT-SUMMARY into feature/v-4-lib-upgrade
…om/uwcirg/AHRQ-CDS-Connect-PAIN-MANAGEMENT-SUMMARY into feature/v-4-lib-upgrade
…PAIN-MANAGEMENT-SUMMARY into feature/v-4-lib-upgrade
…PAIN-MANAGEMENT-SUMMARY into feature/v-4-lib-upgrade
…PAIN-MANAGEMENT-SUMMARY into feature/v-4-lib-upgrade
in favor of #153 |
based on changes from latest release from original AHRQ repo
Changes brought in are:
Factors_to_Consider_in_Managing_Chronic_Pain_FHIRv401.cql
and newVSACAwareCodeService
function to extract OID from VSAC URL inexecuteELM.js
Changes made as a result of CQL and FHIR version updates:
Dispensed date
obtained via the extension in a Medication Request FHIR object to be of data typeFHIR.date
doseQuantity
used in a MED calculation to be of data typeSimpleQuantity
LastPositionOf
and useSplit
Other changes: