Skip to content

Latest commit

 

History

History
536 lines (406 loc) · 41.5 KB

CHANGELOG.md

File metadata and controls

536 lines (406 loc) · 41.5 KB

Consent2Share 3.4.0 (2017-09-18)

Consent2Share 3.4.0 is the Fifth release of Consent2Share V3. The work on Consent2Share V3 is based on Consent2Share V2.

The overarching goal for Consent2Share V3 is to build a FHIR-centric, componentized, and cloud-based (cloud native) application.

Features

  • i18n (Internationalization) support is added for database lookup values.
  • Document segmentation service configuration support is improved to handle multiple document template configurations.
  • C-CDA R2.1 Care Plan document segmentation is added to the document segmentation service.
  • Notification is given when account locked because of failed login attempts.
  • Patient can get health data from HIE XDS.b repository.
  • IExHub is separated into two spring boot services iexhub-xdsb and iexhub-pix-pdq with clean and generated IHE Soap clients.
  • Apache PDFBox is used to generate PDF.
  • Fixed critical security vulnerabilities found in the static scan.
  • Fixed bugs.

Documentation Updates

The following documents have been updated:

  • C2S Master User Guide
  • C2S Provider User Guide
  • C2S Staff User Guide
  • C2S Patient User Guide
  • C2S Deployment Guide
  • C2S Development Guide

Also README.md files in repositories and Docker image descriptions are updated as well.

NOTES:

Consent2Share 3.4.0 release includes:

Consent2Share 3.3.0 (2017-08-07)

Consent2Share 3.3.0 is the Fourth release of Consent2Share V3. The work on Consent2Share V3 is based on Consent2Share V2. Version 3 is still in progress and one more release will come over the next month.

The overarching goal for Consent2Share V3 is to build a FHIR-centric, componentized, and cloud-based (cloud native) application.

Features

  • Single login UI
  • Consent activity history
  • Trying my policy sample document update
  • Configurable patent search fields
  • UI styling update
  • Patient Registration/Update in HIE
  • New PIX Client
  • Update Patient profile (with Avatar)
  • Try my policy for provider
  • Multiple identifier support for patient

Documentation Updates

The following documents have been updated:

  • C2S Deployment Guide
  • C2S Provider User Guide
  • C2S Patient User Guide

Also README.md files in repositories and Docker image descriptions are updated as well.

NOTES:

Consent2Share 3.3.0 release includes:

Consent2Share 3.2.0 (2017-06-27)

Consent2Share 3.2.0 is the Third release of Consent2Share V3. The work on Consent2Share V3 is based on Consent2Share V2. Version 3 is still in progress and more releases will come over the next 3 months.

The overarching goal for Consent2Share V3 is to build a FHIR-centric, componentized, and cloud-based (cloud native) application.

Features

  • EHR integration push model
    • provider manages patient, provider creates consent for patient to sign, provider segment C-CDA for downloading.
  • Try My Policy Feature.
  • Auditing upate.
  • Update document validator.

Documentation Updates

The following documents have been updated:

  • C2S Deployment Guide
  • C2S Provider User Guide
  • C2S Patient User Guide

Also README.md files in repositories and Docker image descriptions are updated as well.

NOTES:

Consent2Share 3.2.0 release includes:

Consent2Share 3.1.0 (2017-05-09)

Consent2Share 3.1.0 is the second release of Consent2Share V3. The work on Consent2Share V3 is based on Consent2Share V2. Version 3 is still in progress and more releases will come over the next 6 months.

The overarching goal for Consent2Share V3 is to build a FHIR-centric, componentized, and cloud-based (cloud native) application.

Features

  • Styled consent2share UI.
  • Data segmentation with FHIR consent and share logic.
  • Staff admin is able to register/manage patient user
  • C2s-ui support i18n.

Documentation Updates

The following documents have been updated:

  • C2S Deployment Guide
  • C2S Patient User Guide

Also README.md files in repositories and Docker image descriptions are updated as well.

NOTES:

Consent2Share 3.1.0 release includes:

Consent2Share 3.0.0 (2017-03-31)

Consent2Share 3.0.0 is the first release of Consent2Share V3. The work on Consent2Share V3 is based on Consent2Share V2. Version 3 is still in progress and more releases will come over the next 6 months.

The overarching goal for Consent2Share V3 is to build a FHIR-centric, componentized, and cloud-based (cloud native) application.

Features

  • The patient user can login to a card-based, componentized UI.
  • The patient user can add his or her providers by looking up providers using the card-based, componentized UI.
  • The patient user can create, sign, revoke, and delete his or her consent using the card-based, componentized UI.
  • When creating a consent, the patient user can chose “Share” instead of “Not Share”.
  • The consent created by the patient user is stored in FHIR STU3 format in the FHIR server.
  • The patient user UI is redesigned and rewritten in Angular.
  • Core services are decoupled from the UIs by using backend for frontends (BFF) pattern.
  • The domain for patient consent management is redesigned to focus only and focus well on consent.

Documentation Updates

The following documents have been updated:

  • C2S Deployment Guide
  • C2S Patient User Guide

Also README.md files in repositories and Docker image descriptions are updated as well.

NOTES:

Consent2Share 3.0.0 release includes:

Consent2Share 2.1.2 (2017-07-25)

Features

Node.js released a security update on July 11, 2017. Node.js stated that updates are now available for all active Node.js release lines. These include the fix for the high severity vulnerability identified in a previous announcement, one additional lower priority Node.js vulnerability in the 4.x release line, as well as some lower priority fixes for Node.js dependencies across the current release lines.

The following Consent2Share projects have been enhanced to accommodate the most recent LTS version of Node.js (6.11.1), which includes the security updates:

  • Patient Portal UI
  • Admin Portal UI

Consent2Share V2.1.2 does not affect build artifacts such as JARs and Docker images which were made available during release V2.1.1. You can continue to use the latest Docker images from the Docker Hub. However, if you are currently coding, contributing to our code base, and building your own binary artifacts from the Consent2Share source code, make certain to use Consent2Share V2.1.2, which accommodates the Node.js 6.11.1 security update.

NOTES:

Consent2Share 2.1.2 release includes:

Consent2Share 2.1.1 (2017-03-22)

Features

The following projects have been enhanced to support internationalization (i18n):

  • Patient Portal UI
  • Admin Portal UI
  • Patient User API
  • Patient Consent Management API
  • Patient Health Record API
  • Try My Policy API

The supported languages in Consent2Share Release 2.1.1 are English (en_US) and Spanish (es_ES). This work was done in collaboration with Adela Grando, Assistant Professor, Biomedical Informatics, Arizona State University, and her student Wentao Zhou.

Documentation Updates

The following documents have been updated:

  • C2S Admin User Guide
  • C2S Patient User Guide

Also, the README.md files in the repositories for the APIs listed above and the latest tag in Docker image descriptions are updated as well.

NOTES:

Consent2Share 2.1.1 release includes:

  • Configuration Data 2.1.1 - Clone the master branch - Reset the code to Release 2.1.1 commit - It will run only with master branch.

Consent2Share 2.1.0 (2017-02-06)

Features

  • Consent Management: Supports FHIR Consent STU3 to publish to a FHIR server
  • Provider Lookup Service: Rewritten to use Spring Boot for implementation, which is in line with other components’ implementation
  • Configuration Server: Supports source-controlled configuration data for Spring Boot Microservices
  • UI: Support writing Angular 2.0 style web component
  • Information Exchange Hub:: Supports FHIR Consent STU3 as a FHIR server and support flexible configuration location for the application to run
  • Easier Local Development setup by removing required Maven global settings
  • Upgraded Spring Boot and Spring Cloud dependencies

Documentation Updates

The following documents have been updated:

  • C2S Development Guide
  • C2S Deployment Guide
  • C2S Technical Blueprint

Also README.md files in repositories and Docker image descriptions are updated as well.

NOTES:

Consent2Share 2.1.0 release includes:

  • Configuration Data 2.1.0 - Clone the master branch - Reset the code to Release 2.1.0 commit - It will run only with master branch.

Consent2Share 2.0.0 (2016-10-31)

Features

  • Patient Registration: Collect patient demographic and register patient in Consent2Share and HIE (if connected)
  • Security: Use OAuth 2.0 and OpenID Connect for authentication and authorization
  • Provider Management: Allow patients to search, delete, and manage their providers
  • Consent Management: Allow patients to create, sign, and revoke consent policies that determine the level of privacy applied to the patient’s health record when it is shared between providers
  • Try Policy: : Allow patients to use the Try My Policy tool against a medical record in order to view the effects of their consent directive segmentation choices
  • Value Set Management: Provide an API to determine sensitivity categories for medical record entries
  • Data Segmentation: Handle the segmentation of patients’ sensitive health information according to their consent directive
  • View PHI: Allow patients to view medical records and health information retrieved from an HIE (if connected)
  • Document Validation: Provide an API to validate C32, C-CDA R1 and 2.1 documents based on schema and/or schematron rules

NOTES:

Consent2Share 2.0.0 release includes:

//: # (# x.x.x (yyyy-mm-dd)

//: # (* Patient Portal UI x.x.x: release url //: # (* Admin Portal UI x.x.x: release url