eTB Manager Desktop

So we will test it on another way:

- Improve SyncClear Annotation, changing it propose to annotate details about sync.
- Implement parameters on that annotation to verify what the sync should do about it, like, clear = true, keyparameter = true...
- While synchronizing, it it is a new entity (serverId is null) check if there is any other entity with the same key parameters, for example, for a tbcase it should be registration date. For patient, should be the name, mothername and birthdate. If exists any other entity with thiose key parameter equals the ones of the new entity coming from sync the system should merge those objects.

Case side effect nao foi feito o controle, pq no generico seriam utilizados o mes, tbcase e o sideeffect, mas em bangla seria utilizado o sideeffect, tbcase e a data inicial.

Solução: popular o mês automaticamente e usar em bangla mês, data inicial e case.

Check bellow the attrbutes being used on the search of similar entities

TbCase - patient e registration date
Exam culture, microscopy, xpert, dst, skin, biopsy - date collected, laboratory, tbcase
Medical examinarion, exam hiv, exam xray - data, tbcase.
Casesideeffect - pending - mês, tbcase, sideeffect, and initial date for bangladesh
tbcontact - tbcase, name, gender, age
Commorbiditie - no need, diferent way of importing.
Patient - need to check!

updating:

TbCase - patient e registration date
Exam culture, microscopy, xpert, dst, skin, biopsy - date collected, laboratory, tbcase
Medical examinarion, exam hiv, exam xray - data, tbcase.
Casesideeffect - pending - mês, tbcase, sideeffect, and initial date for bangladesh
tbcontact - tbcase, name, gender, age, typeof contact
Commorbiditie - no need, diferent way of importing.
Patient - pending

tbcase and patient verification need to be improved and tested
casesideeffect need to be reinvented because of the explained above.

tbcase and patient verification need to be improved and tested - STILL PENDING
casesideeffect need to be reinvented because of the explained above. - DONE

A verificação do tbcase e patient sera feita no mesmo momento. Atributos que seão analisados:

-owner_id
-diagtype
-notifid
-regdate
-patient ref by

-name
-age
-gender

Está pronto, verificar aval do ricardo:
- O problema é que em bangl muitas pessoas tem o mesmo nome, sera que os atributos acima são o suficiente?
- Quando cadastra um caso é criado tb um medicalexamination, porem, como o caso ainda nao tem case_id no lado do servidor, fica dificil determinar qual o caso desse medicalexamination(nao existe tbcase.id no params do medical examination) que esta sendo criado, pq nao vem na lista de parametros! Isso tb pode acabar acontecendo com casos novos que já possuem exames cadastrados mas nunca foram sincronizados.