Sync 2.0 Project daily stand-ups

Blocked?

  • No.

What I’ve done:

  • SYNCT-242: Implement conflict detection and resolution - backend
  • SYNCT-240: Find the best way of conflict detection and resolution

What’s next:

  • SYNCT-242: Implement conflict detection and resolution - backend
  • SYNCT-240: Find the best way of conflict detection and resolution

Blocked?

  • No.

What I’ve done:

  • SYNCT-235: Add logic for TestOrder synchronization
  • SYNCT-209: Synchronize Allergy via FHIR and Rest
  • SYNCT-234: Add logic for DrugOrder synchronization

What’s next:

  • SYNCT-235: Add logic for TestOrder synchronization

Blocked?

  • No.

What I’ve done:

  • SYNCT-242: Implement conflict detection and resolution - backend
  • SYNCT-243: Create interface for extension points
  • SYNCT-252: Implement generic hashCode function

What’s next:

  • SYNCT-243: Create interface for extension points
  • SYNCT-252: Implement generic hashCode function
  • SYNCT-209: Synchronize Allergy via FHIR and Rest

Blocked?

  • No.

What I’ve done:

  • SYNCT-235: Add logic for TestOrder synchronization
  • SYNCT-212: Form object should be synchronized
  • SYNCT-251: Create service for saving hashcodes to database
  • SYNCT-209: Synchronize Allergy via FHIR and Rest
  • SYNCT-234: Add logic for DrugOrder synchronization

What’s next:

  • SYNCT-251: Create service for saving hashcodes to database

Blocked?

  • No.

What I’ve done:

  • SYNCT-254: Create service for saving conflicts to database
  • SYNCT-251: Create service for saving hashcodes to database

What’s next:

  • SYNCT-254: Create service for saving conflicts to database

Blocked?

  • No.

What I’ve done:

  • SYNCT-242: Implement conflict detection and resolution - backend
  • SYNCT-240: Find the best way of conflict detection and resolution
  • SYNCT-244: Implement conflict detection and resolution - frontend

What’s next:

  • SYNCT-244: Implement conflict detection and resolution - frontend

Blocked?

  • No.

What I’ve done:

  • SYNCT-252: Implement generic hashCode function

What’s next:

  • SYNCT-252: Implement generic hashCode function
  • SYNCT-251: Create service for saving hashcodes to database

Blocked?

  • No.

What I’ve done:

  • SYNCT-256: Sprint 12 planning 15.11.2018
  • SYNCT-255: Unify pulled object
  • SYNCT-252: Implement generic hashCode function
  • SYNCT-239: Sprint 11 retrospective 15.11.2018

What’s next:

  • SYNCT-255: Unify pulled object

Blocked?

  • No.

What I’ve done:

  • SYNCT-256: Sprint 12 planning 15.11.2018
  • SYNCT-235: Add logic for TestOrder synchronization
  • SYNCT-239: Sprint 11 retrospective 15.11.2018

What’s next:

  • SYNCT-265: Milestone 1 - showcase

Blocked?

  • No.

What I’ve done:

  • SYNCT-256: Sprint 12 planning 15.11.2018
  • SYNCT-244: Implement conflict detection and resolution - frontend
  • SYNCT-239: Sprint 11 retrospective 15.11.2018

What’s next:

  • SYNCT-244: Implement conflict detection and resolution - frontend

Blocked?

  • No.

What I’ve done:

  • SYNCT-265: Milestone 1 - showcase
  • SYNCT-244: Implement conflict detection and resolution - frontend

What’s next:

  • SYNCT-244: Implement conflict detection and resolution - frontend

Blocked?

  • No.

What I’ve done:

  • SYNCT-256: Sprint 12 planning 15.11.2018
  • SYNCT-254: Create service for saving conflicts to database
  • SYNCT-253: Implement conflict detection
  • SYNCT-251: Create service for saving hashcodes to database
  • SYNCT-239: Sprint 11 retrospective 15.11.2018

What’s next:

  • SYNCT-253: Implement conflict detection

Blocked?

  • No.

What I’ve done:

  • SYNCT-205: Setup UI tests environment for FHIR mapping
  • SYNCT-265: Milestone 1 - showcase

What’s next:

  • SYNCT-205: Setup UI tests environment for FHIR mapping

Blocked?

  • No.

What I’ve done:

  • SYNCT-255: Unify pulled object
  • SYNCT-265: Milestone 1 - showcase

What’s next:

  • SYNCT-255: Unify pulled object
  • SYNCT-252: Implement generic hashCode function

Blocked?

  • No.

What I’ve done:

  • SYNCT-245: Integrate conflict resolution with the current Sync 2.0 audit log interface

What’s next:

  • SYNCT-245: Integrate conflict resolution with the current Sync 2.0 audit log interface
  • SYNCT-244: Implement conflict detection and resolution - frontend

Blocked?

  • No.

What I’ve done:

  • SYNCT-253: Implement conflict detection
  • SYNCT-265: Milestone 1 - showcase

What’s next:

  • SYNCT-253: Implement conflict detection

Blocked?

  • No.

What I’ve done:

  • SYNCT-205: Setup UI tests environment for FHIR mapping

What’s next:

  • SYNCT-205: Setup UI tests environment for FHIR mapping

Blocked?

  • No.

What I’ve done:

  • SYNCT-245: Integrate conflict resolution with the current Sync 2.0 audit log interface

What’s next:

  • SYNCT-245: Integrate conflict resolution with the current Sync 2.0 audit log interface
  • SYNCT-244: Implement conflict detection and resolution - frontend

Blocked?

  • No.

What I’ve done:

  • SYNCT-253: Implement conflict detection

What’s next:

  • SYNCT-253: Implement conflict detection

Blocked?

  • No.

What I’ve done:

  • SYNCT-270: Milestone 1 regression testing

What’s next:

  • SYNCT-270: Milestone 1 regression testing