Re: ID replacing DS in COGA docs

I do agree with John. If we try to capture all variables we may miss some of them. Down syndrome is common but does display similar intellectual disabilities of other common and less common disabilities. It makes sense to use the broader term. Thanks for leading the conversation John. 

Debra Ruh, Ruh Global Communications & AXSChat 
Global Accessibility and Disability Inclusion Strategist 
G3ict Employability & Technology Chair
(804) 986-4500 
Debra@RuhGlobal.com
www.RuhGlobal.com

Follow Me on twitter,linked-in, facebook,pinterest, tumblr, Google+
And SKYPE at debraruh 

Proud to announce my book “Find Your Voice using Social Media” http://ow.ly/kxglR

My 2nd book "Uncovering Hidden Human Capital: How Leading Corporations Leverage Multiple Abilities in Their Workforce" will be published in 2015.








> On Jul 13, 2015, at 8:33 AM, Rochford, John <john.rochford@umassmed.edu> wrote:
> 
> Hi All,
>  
> As you may know Down Syndrome is one many intellectual disabilities. In some of our weekly teleconferences, I have suggested that we replace Down Syndrome with Intellectual Disability in our documentation, but cite Down Syndrome as one example of it. I know Debra supports this, and I believe Neil does too.
>  
> Several weeks ago, I replaced “Down Syndrome” with “Intellectual Disability” in the user-research text. I also created a gap analysis for Intellectual Disability (intending to replace the one for Down Syndrome) by basing it on the Down Syndrome one.
>  
> That new content was not published because Lisa responded with “John, I think the idea was to change it in the techniques not the user research Let's check back with the group”.
>  
> I think the replacement should happen in all our documentation, including in user research. I hope we can discuss this in today’s call, and come to a resolution.
>  
> John
>  
> John Rochford
> UMass Medical School/E.K. Shriver Center
> Director, INDEX Program
> Instructor, Family Medicine & Community Health
> www.DisabilityInfo.org
> Twitter: @ClearHelper
>  
>