RuntimeException: unexpected value -1 within Framingham.stroke10Year (VitalSign.SYSTOLIC_BLOOD_PRESSURE is -1) about synthea

[dehall]

Thanks for reporting this issue and providing all the details. I'm able to reproduce everything you've mentioned here, including the fact that the -ps flag doesn't produce the same error which is frustrating. I may split that out into a separate issue.

At a glance, the biggest problem on this patient is with the medications they is on, leading to impacts that decrease their baseline blood pressure by 100. They appear to be on 7 different medications, some from the same drug class, which doesn't sound right (though I'm a software engineer, not a doctor). It looks like those 7 medications are being prescribed for 3 different reasons - hypertension, stable ischemic heart disease, and congestive heart failure. Unfortunately there's a lot of complexity in patients that have multiple chronic conditions, and the logistics of managing those prescriptions isn't being modeled well here.

A quick fix might be to just restrict the "getMedicationImpacts" total to only a certain amount, or apply other bounding limits to different calculations, but I'll keep looking

[dehall]

Also, looks like the reason the -ps flag didn't work is because of how synthea rotates seeds to ensure the correct number of alive patient records are generated and they match the target demographics. If the patient for seed 1 dies before reaching the target age, it has to retry with a new seed to fill that slot. If the same seed were re-used the same thing would happen all over again. For uniqueness and consistency the next seed is a new number based on the first seed.

In this case the seed to use to reproduce the issue without generating the entire population is 4417061940514179057 which is the original, non-rotated seed. (If you debug at the time of the exception and look at person.seed it's 3-something) That's neither obvious nor intended so I'll open a new issue to track that.