Achimedes API sending strange numbers? Showing high risk when not at high risk?

39 views
Skip to first unread message

silverfox

unread,
Oct 31, 2012, 6:21:03 PM10/31/12
to million-hear...@googlegroups.com
It appears to me that the Archimedes API is now giving different answers for the same information.

Its returning 5 for "ratingForAge" when the stats are good and the same numbers were returning 1 just a couple days ago.

 

35yo male 150lbs 5'10 (non smoker no other risks)
BP 120/90
Total cholesterol 150
HDL 60
LDL 90

...yields a 5?  IT seems like the risk assessment number is no longer accurate and now "disagrees" with the Framingham 10year risk calculation.

Example output.
{
    "ElevatedCholesterol": false,
    "ElevatedBloodPressure": false,
    "code": 200,
    "Risk": [
        {
            "rating": "3",
            "risk": "3.61",
            "riskType": "CVD",
            "comparisonRisk": "6.93",
            "ratingForAge": "5",
            "riskPercentile": "99"
        },

Steven Gain

unread,
Oct 31, 2012, 8:46:04 PM10/31/12
to million-hear...@googlegroups.com
I noticed this a few days ago too and spent the day checking my code. II came to the conclusion that they must tweaking the algorithm and left it.

Don Morris

unread,
Nov 1, 2012, 1:46:29 PM11/1/12
to million-hear...@googlegroups.com

We believe the issue in this particular run is an identified bug that arises in the boundary case when LDL+HDL = total cholesterol (which should never happen in real results).  That bug has been resolved and will be fixed in our next release.

 

Don

--
You received this message because you are subscribed to the Google Groups "Million Hearts Challenge" group.
To unsubscribe from this group, send email to million-hearts-cha...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

silverfox

unread,
Nov 1, 2012, 10:02:42 PM11/1/12
to million-hear...@googlegroups.com
Great. Thank you.


So really the validation logic should be HDL+LDL may not exceed OR EQUAL Total cholesterol.  Correct?

Silver Fox


On Thursday, November 1, 2012 1:46:32 PM UTC-4, don.m...@archimedesmodel.com wrote:

We believe the issue in this particular run is an identified bug that arises in the boundary case when LDL+HDL = total cholesterol (which should never happen in real results).  That bug has been resolved and will be fixed in our next release.

 

Don


On Wednesday, October 31, 2012 3:21:03 PM UTC-7, silverfox wrote:

Ayis Pyrros

unread,
Nov 1, 2012, 10:07:25 PM11/1/12
to million-hear...@googlegroups.com
Did something just change with surescripts AP json object. My gmaps interface is acting funny?

Thanks

A


--
You received this message because you are subscribed to the Google Groups "Million Hearts Challenge" group.
To unsubscribe from this group, send email to million-hearts-cha...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Ayis Pyrros ay...@ayis.org

Dave Vockell

unread,
Nov 1, 2012, 11:17:58 PM11/1/12
to million-hear...@googlegroups.com
I am not seeing anything different.

To unsubscribe from this group, send email to million-hearts-challenge+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Ayis Pyrros ay...@ayis.org

Don Morris

unread,
Nov 2, 2012, 11:22:46 AM11/2/12
to million-hear...@googlegroups.com
Yes but the boundary case will work in future

Sent from my iPhone
--
Reply all
Reply to author
Forward
0 new messages