Closed vinayvenu closed 1 week ago
We are currently blocked due to StagingSickelCell app responding with ErrorMsg: "Data could not Saved! due to duplicate record or server issue." for valid requests as well.
In 2 things, the postman collection JSON is not inline with that of sickle cell API documentation:
Some background info., that I came to know from a contacted person that might help in testing: There is a unique contraint validation around the combination of NameOfPerson, SonDaughterOfWifeOf, MobileNo, Gender.
Yes, using qr_code gets it to work. For patient "Gayatri Kewat" the sickle cell registration response is ,
{"Status":200,"Total":1,"Success":1,"fail":0,"Success_records":[{"Status":200,"Message":"Patient information is Successfully Saved .","sickle_id":"24712","patient_unique_id":"SJ00329"}]}
In 2 things, the postman collection JSON is not inline with that of sickle cell API documentation:
- the key name for qrcode is qr_code not qr-code - With this alone, the issue gets resolved
- format of the registration date: It needs to be of the format 'YYYY-MM-DD'
Some background info., that I came to know from a contacted person that might help in testing: There is a unique contraint validation around the combination of NameOfPerson, SonDaughterOfWifeOf, MobileNo, Gender.
After making the above corrections, post of registration data goes through, but only when we specify "health_facility_id" as "424790" and "healthfacilitytype_id" as "5".
@himeshr they are not reply via mail, so I suggest whoever is going to pickup contact the no mentioned in keeweb with name 'Sickle cell help'. Its not the Tapas contact that Vinay has.
@vinayvenu can this be marked as done.?
Tasks list:
Drive folder with relevant docs:
@vinayvenu has the files