Release 3.1.6

The following are the release notes for the release:

Major Updates
Updated the CDA eICR R3.1 generation logic for Production usage.

List of tickets Addressed with specific changes:
#819: Fixed schema errors due to adding Incomplete Section Information for Ignored Resources
#810: Updated Narrative Generation for Problem Section
#809: Return OperationOutcome from receive-notification API
#807: Fix NotificationContextController API parameter ordering
#784: Allow Other Race Category
#758: Update some of the packages to fix SONAR issues.
#711: Fix CDA eICR3.1 generation to eliminate errors.
#624: Add support for Smoking Status in Social History Section
#622: Add support for RouteCode for Immunizations and Medications
#605: Add property for auth token refresh threshold.
#440: Fix CCRR generation logic to account for the profiles required according to the latest CCRR IG.

List of Tickets which cannot be reproduced
#742: Not reproduceable in the current baseline of 3.1.5
#724: Not reproduceable in the current baseline of 3.1.5
#621: Not reproduceable in the current baseline of 3.1.5

List of Tickets fixed in previous baselines
#524: Data requested has been added to the ph_messages in previous baselines.

List of Tickets Not Applicable to eCRNow App
None.

Release 3.1.5

The following are the release notes for the release.

List of tickets Addressed with specific changes:
#798: Added Location Name into Encompassing Encounter when it is present in the FHIR Resource.
#778: Updated author to have the specific App version instead of just 3.X by default.
#772, #745, #734, #723, #645, #608, #586, #531: Updated Lab Result and Plan of Treatment generation for Diagnostic Results and Lab Tests to allow for different combinations of FHIR Resources with and without codes and trigger code insertion logic for matched DiagnosticReports, LabObservation Panels, Organism Substances.
#770: Updated Race and Ethnicity generation to use Text when applicable without codes.
#767: Updated logic to allow for database timezone to be different than JVM timezone and scheduling of timers.
#766, #747, #535: Updated Trigger Code Template insertion logic to account for Encounter Diagnosis and Encounter Reason code elements.
#765, #762, #746: Updated Social History Generation to ensure duplicate travel and occupation observations are not created in the eICR.
#764: Propagated country code from Telecom Contact Point to eICR when present.
#761: Updated Social History generation to remove social history observations not related to travel and occupation.
#760, #744: Updated migration script to fix relaunchPatient/launchPatient unique constraint error.
#757: Fixed eICR Medications Administered section schema error when the timestamp is a single value instead of an interval.
#753:, #369 Fixed launchPatient errors to return OperationOutcome always. Monitoring scripts that vendors may have used previously to look for specific terms would have to be modified to detect errors in launchPatient/relaunchPatient going forward.
#748: Changed Guardian eICR generation logic to account for both FHIR and CDA value sets across different FHIR and US Core versions.
#739: Updated CDA eICR Header generation to use Telecom of type phone instead of fax when both are present and one of them needs to be used in custodian.
#735: Updated Social History generation to incorporate effectiveTime in Travel observations.
#727: Incorporated startup time delay for launchPatient and relaunchPatient config parameter to address spikes during startup related to pending tasks that may be processed immediately.
#722: Author entries have been added to Organizer and Result Observation entries within the Results Section.
#720: Updated LabResults generation capability to handle strings in codes and values.
#708: Added author to the Planned Observation entries.
#707, #361: Updated encompassingEncounter generation to account for different Codesystems while generating encompassingEncounter/code element.
#672: Updated Result generator and Plan of treatment generation to account for different FHIR status values and map them to CDA eICRs.
#632, #502, #410: Updated KAR processing logic to only display ERSD and KAR files that are really present and remove any ERSD’s that are not present anymore. In addition, inactive ERSD/KAR files will continue to work as long as the timers are already setup. These tickets required a schema change to the kar_info table with an additional column that is nullable.
#528: Java 17 is supported on the master as part of the baseline.
#505, #343: Fixed time string formatting in Medication section regardless of FHIR resources namely MedicationAdministration, MedicationStatement, MedicationRequests
#504: Problem Effective Time is now part of the HTML rendering in the problem section.
#492: Added RequestId to logging the identify the scheduled job transaction using log analytics easily.

List of tickets addressed by earlier changes:
#704, #513: Fixed in ERSDv2 or ERSDv3 released previously.
#706: Addressed by other changes in Social History.
#581, #500, #285, #105: Addressed in 3.1.4 or earlier baselines.

List of tickets not addressed and not applicable:
#777, #763, #637, #630, #627, #462,

Unable to Reproduce:
#742,

Release 3.1.4

The following are the changes in Release 3.1.4

1. Updates to handle ERSDv3
2. Custom Query configuration has been changed for ERSDv3. ERSDv2 remains the same. Please refer to the https://github.com/drajer-health/eCRNow/blob/master/CustomQueryConfiguration.md for the latest instructions.
3. Support for Java 17 and Java 8 on the same baseline. Java Version can be supplied as part of the command line using the variable JAVA.VERSION. Please refer to the README.md for the specific instructions.
4. Support for additional interceptors to be added to HTTP Headers for Multi-tenant use cases.
5. Modified launchPatient to not allow duplicate launches.
6. Modified relaunchPatient to allow duplicate relaunches.
7. Added logic to handle Travel History components in Observations
8. Added Estimated Date of Delivery template.
9. Added support for multiple Spring profiles to enable better testing across environments.
10. Fixed Fatal errors due to Encounter reasonCode.
11. Updated log statements to reduce VeraCode findings.
12. The following tickets have been addressed as part of the release.
    #688, #685, #684, #683, #682, #681, #679, #678, #677, #676, #671, #669, #666, #665, #657, #654, #651, #648, #640, #636, #634,
    #623, #616, #615, #612, #592, #579, #574, #564, #562, #551, #550, #546, #545, #507, #506, #418, #326, #292

Release 3.1.3

The release has the following features added

Support for testing CDA eICR per eCR CDA Release 3.1
Support for testing FHIR eICR per eCR FHIR IG Release 2.1
Tickets and defects that have been resolved in this release include:
646, 644, 643, 642, 641, 629, 628, 625. 624, 610, 609, 602, 601, 584, 578, 577, 565, 562, 559, 542, 539, 529, 523, 522, 514,

Release 3.1.2

The following features are part of the release

1. Further EHR customization of queries using custom queries
2. Support for different configuration parameters for Ambulatory and Inpatient encounters
3. Support for EHR customization pacakges
4. Added APIs for Heatlhcare Settings
5. Added APIs for PhMessages
6. Added APIs for Notification Context
7. eICR generation fixes for narratives

The following defects have been fixed in the release
#614 #603 #602 #590 #589 #585 #571 #569 #568 #567 #563 #561 #555 #553 #548 #547 #537 #536 #532 #531 #525 #524
#523 #522 #521 #519 #518 #507 #506 #505 #504 #503 #496 #478 #477 #467 #450 #445 #428 #381 #358 #325 #280

Releae 3.1.1

The following are the capabilities present in Release 3.1.1

1. Ability to support multiple ERSD versions.
2. Ability to support custom queries
3. Ability to cache data and not requery EHRs for the same transaction
4. Updates to db-scheduler
5. Added Fhir Path Expression evaluator capability
6. Resolved multiple content issues identified for R4.
7. Ability to support off-hour scheduling.
8. Ability to throttle requests.

Release 3.0.0

This is the eCRNow release with the following capabilities.

1. Framework to process multiple plan definitions.
2. Ability to configure plandefinitions by healthcare settings
3. Integrated FhirPath Processor library.
4. Integrated CQL Processor library.
5. Integrated measure processing library.
6. Integrated Backend authorization services client capability.
7. Updated US PH PlanDefinition conditions and actions per the US PH Value Sets.
8. Handle new eCR PlanDefinition.
9. Ability to handle MedMorph Knowledge Artifacts.
10. Framework to support MedMorph use cases.

Release 2.0.0

This is version 2.0.0 of the eCRNow app which is currently being used in production settings.

The summary of changes since Version 1.0.0 are as follows:

1. Tracking requests and responses by eICR Document Id and X-Request Id as needed.
2. Adding mechanism to persist Reportability Response in EHR using Document Reference.
3. Adding mechanisms to fetch paginated resources from EHRs.
4. Added support for Travel History, Pregnancy status
5. Added persistent timer mechanisms for scalability and fault tolerance.
6. Added support for RESTful API to integrate with work flows.
7. Added validation mode to launch API to produce eICR for verifications.
8. Split the eCRNow UI into a different project.
9. Fixed issues with CloseOutEicr and PeriodicEicr not getting generated properly.
10. Resolved Sonarqube identifeid issues for high criticality errors.
11. Added unit tests to improve code quality.
12. Fixed issues with various CDA errors using FHIR R4 to CDA converter.
13. Provided ability to customize Authentication/Authorization methods for workflow integration.
14. Provided capabilities to inject security key for encryption using environment variables.
15. Added better logging and timestamps across all tables.

Bug Fixes to FHIR R4 and DSTU2 for CDA Generation.

The release has the following updates from the previous version

Release Notes:

1. Add Matching Triggers based on Full ECR and COVID simultaneously.
2. Add checks to avoid duplicate messages being sent to PHA.
3. Added Support for Social History Section for Birth Sex.
4. Added OID to URL Mapping properties file.
5. Added FHIR R4 to CDA Conversion along with fixes for DSTU2.
6. Added action to check Reportability Responses.
7. Added checks for FHIR R4 in ECA actions to invoke appropriate conversions.

1.0 Release

The release has the following updates from the previous version

Release Notes:

1. Addition of Schema validation.
2. Fixes for Schema and Schematron validation failures.
3. Handling of Immunization/Diagnostic orders Sections.
4. Fixes for Direct Messaging.
5. Added actions to recheck trigger codes based on a frequency.
6. Added Trigger code checks upon initiation, creation of eicr and close out of eicr.
7. Adding Editing feature for Client details collections.
8. Added headless launch and redirect capabilities for the app.
9. Fixed Duplicate entries in the XML files.
10. Fixed duplicate messages being sent out.
11. Optimized trigger code checking in the workflows and eliminated redundancy.