Releases: onc-healthit/reference-ccda-validator
1.0.45 - Cures Update 1
1.0.44
Release Notes:
- Add dynamic issue count for total IG Conformance error checks to the API
- Add vocabulary configuration error checks count to the API
Detailed Changes by Commits:
@drbgfc
Add support for vocabularyValidationConfigurationsErrorCount …
f0b920b
@drbgfc
test: Add support for vocabularyValidationConfigurationsErrorCount
21e5f9e
@ssaudacious
fix version number
e8d4c84
@ssavarala
fix github vulnerability
65fbb44
@ssavarala
update github links
5010e28
@drbgfc
Update artifactory server name and IP address
620b239
@drbgfc
Revert artifactory back to old AHRQ server
d7a1ec3
@drbgfc
Update pom for Scorecard UI Update and fix existing version issues
102965d
1.0.43: Merge pull request #65 from onc-healthit/develop
-- Fix GitHub security vulnerabilities
-- Update Github link to point to the new repository
-- Add support for vocabularyValidationConfigurationsErrorCount
-- Adds tracking for errors only in total vocabulary validations run
1.0.42
--Add severityLevel to JSON response …
-SITESITE-3013 - This flag can be used to determine whether the results
returned are 0 because there are no issues or because they were limited
by severityLevel
248052e
--Send severityLevel to the Content Validator …
-SITE-3015 Ref Val / Content Val: Suport Content validation process
limiting using severityLevel
a4627d1
-Update readme to new org siteadmin->onc-healthit
656c410
1.0.41
Remove BOM from UTF-8 encoded file (String) if present
-The C-CDA Validator now indirectly supports UTF files encoded with a BOM by removing the BOM before processing.
b2dce3c
Support severityLevel limiting
-The Reference C-CDA Validator API and static UI in local instantiations now support limiting MDHT Conformance and Vocabulary Validation results via their severity (Content limiting is coming soon). This has the potential to offer significant performance gains for users only interested in specific types of results, expecially on larger or issue-prone files. To use the feature, either use the static UI, or, send body form-data key:severityLevel and value:ERROR, WARNING, or INFO. Please note that selecting INFO will return all results, WARNING will return warnings and errors, and ERROR will return errors only.
Related commits:
-Add severityLevel to API, support MDHT results, add tests, update UI …
2903f55
-Support severityLevel limiting in the Code Validator
ce8620d
-Remove severity from NodeCodeSystemMatchesConfiguredCodeSystemValidator …
--NodeCodeSystemMatchesConfiguredCodeSystemValidator defaults to SHALL so
providing a severity has no effect and makes it look like it's doing
something it is not
94b649f
-See https://github.com/siteadmin/code-validator-api/releases/tag/1.0.21 for code val specific severityLevel updates
Enable dynamic config in prod profile (production WAR supports and runs with a dynamic config by default)
845baf4
1.0.40
Note: The configuration file (ccdaReferenceValidatorConfig.xml) has been included as it must be updated for local installations. This can be found in master as well.
Configure the new UnitAllowsOneValidator and update CONF:1198-8559
-In certain scenarios, specified by the configuration file, configuring
UnitAllowsOneValidator will allow unit to be equal to 1. A relevant
scenario is when there is no other option and the value set is UCUM.
-See Jira Ticket SITE-2975
ETT GG "Reference C-CDA Validation Error for Result": unit=1 leads to
invalid vocab error
-See ETT thread:
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/edge-test-tool/SUEm6-EfWQE/NkDPOWTECAAJ
-CONF:1198-8559 was updated to:
--display its rule in the config:
---SHOULD contain zero or one [0..1] value (CONF:1198-8559). a. If
Observation/value is a physical quantity (xsi:type="PQ"), the unit of
measure SHALL be selected from ValueSet UnitsOfMeasureCaseSensitive
(2.16.840.1.113883.1.11.12839) DYNAMIC (CONF:1198-8555)
---Enforce the "If Observation/value is a physical quantity
(xsi:type="PQ"), the unit of measure SHALL be selected from ValueSet
UnitsOfMeasureCaseSensitive (2.16.840.1.113883.1.11.12839) DYNAMIC
(CONF:1198-8555)." portion of the rule which was not enforced prior to
this update
5427aa0
Update readme to clarify config location
ff415d0
Improve readme: java/tomcat/scenarios/war/config
b11b7c4
Update readme with example directory structure
c2899df
Update readme formatting and tomcat version
65a31be
Add "Troubleshooting" section to the readme
c851c37
1.0.39
--Return total validations run based on count in configured XML …
--Test globalCodeValidatorResults and align with testing framework
--Update jackson.core to 2.9.8 / commons-fileupload to 1.3.3
--Add XML Declaration to vocabulary config files
See https://github.com/siteadmin/code-validator-api/releases/tag/1.0.19 for dependency updates
1.0.38
Summary:
---Update pom to work with MDHT artifacts from new repository
---Update error styling of static-ui
---Add Vagrant C-CDA Validator link to github landing document
Details:
@drbgfc
Update pom version to 1.0.38-SNAPSHOT for dev
ad85717
@drbgfc
Update pom to work with MDHT artifacts from new repository
5cadc2f
@wreiske
Added vagrant box
f8715a4
@desai827
Update Error Styling …
f8cf133
@desai827
updated styling to reflect SITE scheme …
c7f6eb8
@drbgfc
Update Vagrant option description in readme
2f23fd1
@drbgfc
Merge pull request #48 from wreiske/patch-1 …
60988df
@drbgfc
Merge pull request #50 from desai827/patch-1 …
16563b4
@drbgfc
Update version to 1.0.38
d5d922e
Note: There were no changes in the code validator or content validator dependencies for this release
1.0.37
d3f2b0e
-Update config to resolve 'SITE-2913 Lab test result with no units'
62ee8e0
-Update config to resolve missing vocabulary rule for CONF:81-16850
dc70129 | b24cfc4
-Update jackson-databind version due to github identified security issue / Fix jackson dependency issues, upgrade both to 2.9.7
Change(s) in code validator:
https://github.com/siteadmin/code-validator-api/releases/tag/1.0.18
1.0.36
-Match config paths and add dynamic vocab to readme
-Update to use local repo, update versions for release
Change(s) in code validator:
see: https://github.com/siteadmin/code-validator-api/releases/tag/1.0.17