Sync 2.0 Project daily stand-ups

Blocked?

  • No.

What I’ve done:

  • SYNCT-205: Setup UI tests environment for FHIR mapping
  • SYNCT-217: Obs mapping testing automation
  • SYNCT-166: Support for handling different catchment areas

What’s next:

  • SYNCT-217: Obs mapping testing automation

Blocked?

  • No.

What I’ve done:

  • SYNCT-163: Define the scope of manual import/export mechanism through the UI
  • SYNCT-189: Validate child instance Id before SYNC2 push

What’s next:

  • SYNCT-189: Validate child instance Id before SYNC2 push

Blocked?

  • No.

What I’ve done:

  • SYNCT-212: Form object should be synchronized
  • SYNCT-209: Synchronize Allergy via FHIR and Rest

What’s next:

  • SYNCT-209: Synchronize Allergy via FHIR and Rest

Blocked?

  • No.

What I’ve done:

  • SYNCT-211: Create FHIR extensions for BaseOpenmrsData

What’s next:

  • SYNCT-211: Create FHIR extensions for BaseOpenmrsData

Blocked?

  • No.

What I’ve done:

  • SYNCT-191: Make usage of REST client generic
  • SYNCT-208: Create the Sync 2.0 demo environment

What’s next:

  • SYNCT-191: Make usage of REST client generic

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-194: Person is not synchronized

What’s next:

  • SYNCT-194: Person is not synchronized

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-191: Make usage of REST client generic
  • SYNCT-208: Create the Sync 2.0 demo environment

What’s next:

  • SYNCT-191: Make usage of REST client generic
  • SYNCT-208: Create the Sync 2.0 demo environment

Blocked?

  • No.

What I’ve done:

  • SYNCT-189: Validate child instance Id before SYNC2 push

What’s next:

  • SYNCT-189: Validate child instance Id before SYNC2 push
  • SYNCT-186: Modify child to send it’s instanceID to parent

Blocked?

  • No.

What I’ve done:

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

What’s next:

  • SYNCT-191: Make usage of REST client generic

Blocked?

  • No.

What I’ve done:

  • SYNCT-194: Person is not synchronized

What’s next:

  • SYNCT-194: Person is not synchronized

Blocked?

  • No.

What I’ve done:

  • SYNCT-191: Make usage of REST client generic
  • SYNCT-208: Create the Sync 2.0 demo environment

What’s next:

  • SYNCT-208: Create the Sync 2.0 demo environment

Blocked?

  • No.

What I’ve done:

  • SYNCT-194: Person is not synchronized

What’s next:

  • SYNCT-194: Person is not synchronized

Blocked?

  • No.

What I’ve done:

  • SYNCT-189: Validate child instance Id before SYNC2 push

What’s next:

  • SYNCT-186: Modify child to send it’s instanceID to parent

Blocked?

  • No.

What I’ve done:

  • SYNCT-205: Setup UI tests environment for FHIR mapping
  • SYNCT-191: Make usage of REST client generic

What’s next:

  • SYNCT-205: Setup UI tests environment for FHIR mapping
  • SYNCT-217: Obs mapping testing automation

Blocked?

  • No.

What I’ve done:

  • SYNCT-211: Create FHIR extensions for BaseOpenmrsData

What’s next:

  • SYNCT-211: Create FHIR extensions for BaseOpenmrsData

Blocked?

  • No.

What I’ve done:

  • SYNCT-186: Modify child to send it’s instanceID to parent

What’s next:

  • SYNCT-149: Sync of Cohort object not working

Blocked?

  • No.

What I’ve done:

  • SYNCT-208: Create the Sync 2.0 demo environment

What’s next:

  • SYNCT-208: Create the Sync 2.0 demo environment

Blocked?

  • No.

What I’ve done:

  • SYNCT-149: Sync of Cohort object not working
  • SYNCT-211: Create FHIR extensions for BaseOpenmrsData
  • SYNCT-164: Parent should have possibility to decide which children could push data to it
  • SYNCT-208: Create the Sync 2.0 demo environment

What’s next:

  • SYNCT-149: Sync of Cohort object not working