Saturday, August 23, 2014

Some Links About Ferguson

We are almost done with Ferguson, Missouri for this time around.  Did we learn anything?  I think we learned that issues surrounding race are no where near settled, and if anything by voting in a man with brown skin as president, we have highlighted the issues even more.  We may be more polarized, and more potentially divided and explosive now than in any time since the 1950s and 1960s.

I have accumulated an impressive pile of interesting opinion articles and I am going to take this post to share some of them with you.  I will also share a link of a recent court settlement.  I would advise not reading it all in one sitting.  It is just too much.  In fact, the coverage of the events in Ferguson began to take on the same sort of life that post 9/11 coverage began to have back in 2001--and there was only email and the telephone back then for "social media." Take the occasional break.  It is good for the soul.

11 Things white people should stop saying..

A mother's white privilege...

Why white moms need to care...

How many unarmed people have to die..

Why we are mad...

I don't know how to talk to white people...

Poll Shows Division...

Explaining white privilege to a poor white...

for the sake of Michael Brown..

White evangelicals listen...

No Time to be polite...

Since we are going to change the tone a little bit, here is some sage advice for dealing with opinion, comment sections and other malarkey on the internet.  Handling the haters....

we want justice, hair extensions..

Man frustrated by Ferguson..

why the Obama administration sees...

Finally, after all the talk above, and all the angst about white bigotry and prejudice and violence, and everything, there needs to be honest talk about black on black violence and black on white violence.

Beaten to death at McDonald's...

Dear reader, feel free to add any links that you have found informative to your outlook on the events of Ferguson and your own views on "Race Matters."





.

4 comments:

Joel said...

Hi, Nice post I enjoyed reading it. Can I contact you through your email? Please email me back. Thanks!

Thanks!

Joel
JHouston791@gmail.com

Anonymous said...

hotmail login

Bobbi Morton said...

Thanks grreat post

Anonymous said...

The NPI Public Data API is a new, faster alternative to the downloadable NPPES data files. It allows systems to access NPPES public data in real-time, rather than through batched uploads. The API retrieves data from NPPES daily.

Please Note: Issuance of an NPI does not ensure or validate that the Health Care Provider is Licensed or Credentialed. For more information please refer to NPI: What You Need to Know


NPPES Read API Interactive Test Application
API Versions 1.0 and 2.0 are NOW retired, please switch your application to use API Version 2.1 if you have not already done so. The old links https://npiregistry.cms.hhs.gov/api?version=1.0 , https://npiregistry.cms.hhs.gov/api?version=2.0 , and https://npiregistry.cms.hhs.gov/api (without the version flag) will no longer work. Please contact customerserviceNPIenumerator@cms.hhs.gov if you have further questions.

System administrators can use the interactive demo to experiment with generating queries.

API Version Interactive Demo Planned Phase Out Date API Link
Version 2.1 Demo TBD https://npiregistry.cms.hhs.gov/api/?version=2.1
An API query will return a maximum of 200 results per request. The Skip field in the API will let you skip up to 1000 records. By using these two fields with your search criteria, you can get up to a maximum of 1,200 records over six requests.

Descriptions of the fields that may be entered as criteria:

version: Identifies the version of the API to use ("2.1").
number: The NPI Number is the unique 10-digit National Provider Identifier assigned to the provider.
enumeration_type: The Read API can be refined to retrieve only Individual Providers or Organizational Providers. When it is not specified, both Type 1 and Type 2 NPIs will be returned. When using the Enumeration Type, it cannot be the only criteria entered. Additional criteria must also be entered as well. Valid values are:
NPI-1: Individual Providers (Type 1) NPIs
NPI-2: Organizational Providers (Type 2) NPIs
taxonomy_description: Search for providers by their taxonomy by entering the taxonomy description.
name_purpose: Refers to whether the name information entered pertains to an Authorized Official's name or a Provider's name. When not specified, the results will search against a provider's first and last name. AO will only search against Authorized Official name. While PROVIDER will only search against Provider name.
Valid values are:
AO
Provider
first_name: This field only applies to Individual Providers. Trailing wildcard entries are permitted requiring at least two characters to be entered (e.g. "jo*" ). This field allows the following special characters: ampersand, apostrophe, colon, comma, forward slash, hyphen, left and right parentheses, period, pound sign, quotation mark, and semi-colon.
use_first_name_alias: This field applies to Authorized Officials and Individual Providers when not doing a wildcard search. When set to "True", the search results will include Providers with similar First Names. E.g., first_name=Robert, will also return Authorized Officials and Providers with the first name of Rob, Bob, Robbie, Bobby, etc. Valid Values are:
True: Will include alias/similar names.
False: Will only look for exact matches.
Default Value is True