Features include Find Insurance Options, Get Prevention Tips, Compare Care Quality and Understand the Law.

Announcing the new site, HHS Chief Technology Officer Todd Parks said, “It’s a website designed to help you take control of your health care – by putting the power of information at your fingertips. It’s the first website to collect both public and private health insurance options across the nation in a single place. Even better, our insurance options finder automatically sorts through this huge catalog of options to help you identify the ones that may be right for you. Other highlights of the site include extensive information about your rights as a consumer, how to navigate the health insurance marketplace, and how the Affordable Care Act can help you – all tailored to you.”

Video tour:

Visit Healthcare.gov:

Related posts:

1. GovRx: Prescription for immigrant healthcare
2. HITECH Act and government access to private health records
3. UK government launches Spending Challenge: ‘Help us get more for less’

I’m not sure I can recommend reading all of the plans cover to cover, but if you’re an advocate or have a vested interest in the future of a Federal agency, these plans are fascinating peek into each agency’s interior life. It’s not just the content of the plans, which run from exciting to comical to mundane. You can also learn a great deal about how agencies view themselves from the way these plans are presented and marketed. It will come as no surprise that the Department of Justice’s rather unlovely document spends a lot of time thinking about reducing its FOIA backlog. The Department of Energy clearly understands itself to be a first a research organization, based on its flagship data sets. The Department of Defense plan is crisp, to the point, and focuses on getting the behemoth to better collaborate and interact with other agencies, rather than the public.

The organizational psychology betrayed by these plans is for another post. My interest is in where agencies found open source. I’ve long advocated for open source as a concrete, tangible way to encourage collaboration between agencies and between the government and its citizens. I was pleasantly surprised, frankly, to see how many agencies agree. Here’s what I found, in no particular order.

US Agency for International Development

The USAID plan was a total surprise. I had no idea how many open source initiatives were being conducted by USAID. Page 30 contains this gem on their Global Development Commons work:

With over four billion subscribers in the world, the mobile phone is often the key to connecting and exchanging information with people in developing countries. The 2008 USAID Development 2.0 Challenge, implemented by the Global Development Commons, invited innovators and entrepreneurs from around the world to participate in a global competition to seek access to information and build new connections to the global community. Crowdsourcing and Open Innovation have become increasingly important engines of innovation globally, leveraged by the commercial, non-profit, academic and government sectors to identify opportunities and solve problems. USAID’s Development 2.0 Challenge yielded 115 submissions using high impact, low-cost, open source solutions.

The winner among the 115 submissions was the RapidSMS Child Malnutrition Surveillance system, which “enables health practitioners to share and track children’s nutritional information with the touch of a cell phone.”

The agency also operates the Intra-Health OPEN Initiative, which is “a suite of free open source solutions to supply health sector leaders and managers with a collection of new tools.”

Social Security Administration

The Social Security Administration is another open source underdog. Imagine all the pent-up innovation they can unlock once this project is underway:

We are in the process of creating internal capacity to host websites and applications based on open-source software solutions and we look forward to a lively exchange of ideas and program code within the growing Federal open–source software development community;

As part of SSA’s fifth goal, “making government more sustainable”, they see open source software as an essential tool:

We are a Federal leader in the use of Health Information Technology. Our work with the private sector may yield transferable ideas and tools. We will share our results and products as appropriate. For example:

• We look forward to sharing the products of our open–source platform efforts across the growing Federal open–source development community, as well as partnering with other agencies in future endeavors; and
• We are in the process of designing and developing an Electronic Technology Repository for communities of innovation. We expect this repository to employ open–source social networking and other tools to permit users to better manage agency knowledge, avoid unproductive duplication of effort, and share experiences. The repository will support the storage of shared materials and project artifacts, discussion boards, wikis, blogs, subscription feeds, and other pertinent information. We envision sharing these resources with other Federal organizations as well.

Others have criticized open source as being irrelevant to the open government movement, but I think interagency collaboration doesn’t happen anywhere near as often as it should, it can be made easier with open source, and it’s outstanding that the SSA seems to agree.

Department of Defense

The DOD has been using open source software for years. Though I was a bit surprised that it wasn’t explicitly mentioned in the DOD’s open government plan, and even more surprised that the much-hyped forge.mil project isn’t referenced at all, the plan includes a number of initiatives that happen to take advantage of open source tools:

The Wikified Army Field Guide, based on Mediawiki, will allow warfighters to collaboratively edit the Army’s field manuals, allowing the documents to be more accurate and responsive:

…as the battlefield changes rapidly, field manuals must keep pace.  Under the traditional process – in which a select few were charged with drafting and updating field manuals –manuals often failed to reflect the latest knowledge of Soldiers on the ground.

Using the same free software behind Wikipedia, the Army’s “wikified” field manuals invite military personnel – from private to general – to collaboratively update the Army Tactics, Techniques and Procedures Manuals in real time.  In so doing, the Army provides a secure means for battle-tested Soldiers to share their experience and advice from the field.  Wikified Army Field Manuals ensure the men and women who serve our Nation have access to the best possible information when they need it.

This is a very exciting opportunity to capture all the innovation happening “at the edge” and quickly incorporate it into useful, official documentation. It makes so much sense, I’m surprised it hasn’t already been done.

The plan also highlights XMPP, which is a tremendously popular instant-messaging protocol that runs, among others, Google Talk. It may surprise you to learn just how much XMPP’s most popular implementation, Jabber, is already being used inside the DOD. The Defense Connect Online program uses Jabber to provide secure IMs inside the DOD, and they announced in November that this would be opened up to the outside world. Because they standardized on an open standard with robust open source implementations, literally dozens of different chat clients are now available to these non-DOD DCO users.

It’s interesting how both Jabber and the Wiki Field Manual projects aim to improve collaboration, and do so on highly collaborative open source platforms. I don’t think that’s an accident.

Department of Homeland Security

VirtualUSA is DHS’ flagship initiative, which couldn’t be more appropriate. From page 23 of the DHS Open Government plan:

On December 8, 2009, Secretary Janet Napolitano publicly launched Virtual USA (vUSA), an innovative information-sharing initiative that draws on practitioner input to help Federal, State, local and Tribal first responders collaborate to make fast, well-informed decisions. vUSA integrates existing frameworks and investments to provide real-time access to operational information—such as weather conditions; traffic; the location and operational status of critical infrastructure; fuel supplies; availability of emergency shelters and medical facilities; and other critical information—that allows users to improve situational awareness and to respond quickly in emergencies.

vUSA currently operates as two pilots – one in eight southeastern states: Alabama, Georgia, Florida, Louisiana, Mississippi, Texas, Virginia and Tennessee; and the other in five states in the northwest: Alaska, Montana, Idaho, Oregon, and Washington. In Virginia alone, vUSA reduced response times to incidents involving hazardous materials by 70 percent.

VirtualUSA is much more revolutionary than this lets on. It’s a very disruptive piece of software in its space. FCW has a succinct overview of the project’s history and what it means for first responders. DHS is funding this project, based on open source and open standards, in part because it wants to encourage collaborative toolbuilding and cooperation among the states, and also because this capability is too important to be in the hands of a single GIS provider, like Google or ESRI. Because it is an open source project, and uses open standards, VirtualUSA ensures that critical assets are not locked into a single vendor, and simultaneously lower the barrier to entry for new GIS vendors.

Department of Commerce

On page 18 of the Department of Commerce plan, under “Open Source Information Technology”, we find some familiar prose:

Also emerging from Commerce’s Open Government Ideascale community was a suggestion to “become more open through the increased use of open source software.” The Department has already begun using the open source tool, Drupal, for a number of its new websites and plans to increase this use in the future. Using open source technology will allow Commerce to develop new technologies and collaborate more readily with the public and other government agencies, and within the Department itself.

To make this happen, the Office of the Chief Information Officer and the Office of Acquisition Management will be consulted to ensure that open source offerings are fully considered during procurement processes. That consideration will include the value that the Department can receive through increased collaboration with the public and as a contributor to open source communities.

Nothing short of victory at Commerce for Open Source of America, whose suggestion this was. Congratulations!

Department of Labor

You’ll find open source in the strangest places. Until I read Labor’s plan, I didn’t appreciate how much data the Department of Labor is responsible for analyzing and disseminating. With that in mind, it makes perfect sense to find this initiative on page 29:

Create a “Developer’s Corner”

We plan to establish a “Developer Corner” on www.dol.gov/open that specifically targets and engages developers. Our goal is to make it as easy as possible for developers to re-purpose our data, provide feedback, get technical help, bring developers with similar interests together and, ultimately inspire the best possible uses of our data for the benefit of the public. Ideas under consideration include a bug tracking system, RSS feeds for dataset changes, dataset versioning, public code competitions, data authentication, and an ideation platform to prioritize developer needs.

I think every department and agency that distributes data to the public (which is to say, all of them) should follow Labor’s lead and establish their own Developer sites. There’s no better way to stay engaged with this very powerful community.

Health and Human Services

The outstanding NHIN CONNECT project, which has a thriving open source community, got a mention on page 56 of HHS’s plan:

Nationwide Health Information Network – Direct

A key component of the Nation’s emerging health information technology infrastructure is the Nationwide Health Information Network (NHIN) – a set of standards, policies, and services that enable the secure exchange of health information over the Internet. “NHIN Direct” is the latest development in the evolution of the NHIN. It’s an important effort to develop a “lightweight on-ramp” to the NHIN that will enable simple, direct exchanges of information between providers, labs, pharmacies, and consumers — and which will be easy to adopt and implement. In a process that launched on March 1, NHIN Direct is being designed in close collaboration with the community of potential users, with the entire process taking place in the open, in public, on a NHIN Direct wikispace. NHIN Direct will then be implemented in real-world tests and deployments by members of the community – with HHS’s Office of the National Coordinator for Health Information Technology (ONC) playing a coordinating and convening role. The gist of the NHIN Direct strategy is to utilize a community-driven approach to ramp up and power NHIN Direct-powered health information exchange.

I should mention that my employer, Red Hat, is involved in this project.

National Science Foundation

There was nothing explicitly about open source in the NSF’s open government plan, but their plan is worth mentioning anyway, as the NSF already does a tremendous amount of work in the open source community. Here’s a search for “open source” on their web site, which yielded over 5,000 hits when I last tried it:

http://search.nsf.gov/search?access=p&output=xml_no_dtd&sort=date:D:L:d1&ie=UTF-8&btnG=Google+Search&client=NSF&oe=UTF-8&proxystylesheet=NSF2&site=NSF&q=open+source

NSF regularly awards grants under the condition that software developed under those grants is given an open source license. Some very progressive thinking, and shrewd IP stewardship from the NSF folks, so we’ll forgive them for not mentioning open source directly in their plan.

Department of the Treasury

Yet another revelation. Treasury plans to cultivate open source projects to facilitate collaboration between agencies and between Treasury and the public. I’ve written about exactly this kind of collaboration before, back in December, so I’m enormously pleased to see that Treasury agrees. I’ve emphasized my favorite passages here:

In the areas of transparency, participation, collaboration, and flagship initiative, Treasury strives to share its efforts across Government to avoid duplication across agencies and to improve value/outcome of efforts. Treasury seeks to manifest cross-agency transferability in at least two of the following ways:

• Make training available to other agencies by opening up classes/webcasts to other agencies; providing slides, video and/or audio after the training; and posting on an e-learning platform.
• Name an advocate who gets the word out about what the agency has to share and invites other agencies to contact that person to learn from him or her.
• Design procurements for enterprise (where government is the enterprise) or in such a way that what is created can be shared across government at no cost.
• Develop and post code so it can be shared with other agencies (open source or the contract written such that the government owns the code.)
• Share platforms utilized by the agency with other agencies at no cost.
• Create participatory events across agencies with related missions.
• Collaborate on projects and challenges with the public and with the private sector in partnership with other federal agencies that have similar missions.
• Share all materials, results, tools, and training that could be transferable to other agencies with the Interagency Working Group as an efficient central dissemination mechanism.

Veteran’s Administration

The VA is an enormous consumer of information technology, and gained early recognition from the open source community for its public domain VISTA electronic health record platform. On page 22 of the VA plan, it becomes clear that the VA is expanding its use of open source to lower the barrier to entry for developers who want to help the agency:

AViVA

A Virtual Installation of VistA Architecture (AViVA) is a recent innovation that we are using to support collaboration. AViVA creates a universal user interface for the electronic health record and includes prototyping of data connectors in order to securely link the AViVA platform to patient data from any source. The AViVA project incorporates HealtheVet as an update of the VistA legacy database system.

VA’s current electronic hospital management system uses a graphical user interface known as the Clinical Patient Record System (CPRS). CPRS data is stored in the legacy data system known as VistA. CPRS requires installation on each machine that operates the program rendering the program difficult to scale and expensive to maintain and update. AViVA’s implementation improves this model in two ways. First, AViVA creates a modular, web-enabled electronic health record system that can be easily and remotely maintained. Second, Medical Data Web Services (MDWS), which can be accessed by the Department of Defense, will allow the creation of applications for any data source to be plugged into the system.

AViVA is a very exciting program for the collaboration portion of our Open Government Plan and because we are committed to creating systems that allow health care providers to collaborate to provide the best care for Veterans. AViVA’s web based presentation layer will allow our doctors and nurses around the country to search patient records as simply and succinctly as you can search for pizza on Google Maps and as securely as the best retail financial service businesses. Additionally, AViVA creates collaboration between VA and DoD, our partner in caring for our nation’s heroes. Finally AViVA creates an open source platform that allows software to be shared with entities outside of VA, creating opportunities for further innovation and development beyond the agency.

National Aeronautic and Space Administration

“NASA is working to make open source software development more collaborative at NASA to benefit both the Agency and the public,” it says right on the first page of the NASA open government plan. Here’s an agency which has always relied on a vibrant research community, software developers, and a culture of innovation. I’m not surprised by their focus on open source, but I am delighted. Among other things, NASA will be sponsoring an open source code competition, has an entire section of their plan devoted to open source development, and will be developing their Nebula cloud computing system on open source software.

It’s fair to say that NASA’s plan is the strongest I’ve seen for the open source community.

Your Turn

Who did I miss? What other opportunities for open source have you found in the open government plans? Leave a comment and let us all know!

Related posts:

1. Flagship Initiatives Shine in Open Government Plans
2. Quick links: Federal agency open government plans
3. Open source matters to open government. Really.

From the White House:

The Plans will make operations and data more transparent, and expand opportunities for citizen participation, collaboration, and oversight. These steps will strengthen our democracy and promote accountability, efficiency and effectiveness across the government.

Here are direct links to all plans (those not linked are not available or not easily visible, so let me know if you find them):

• Agency for International Development
• Department of Agriculture
• Department of Energy
• Department of Education
• Department of Commerce
• Department of Defense
• Department of Health and Human Services
• Department of Homeland Security
• Department of Housing and Urban Development
• Department of the Interior
• Department of Justice
• Department of Labor
• Department of State
• Department of Transportation
• Department of the Treasury
• Department of Veterans Affairs
• Environmental Protection Agency
• General Services Administration
• National Aeronautics and Space Administration
• National Science Foundation
• Nuclear Regulatory Commission
• Office of Personnel Management
• Small Business Administration
• Social Security Administration
• Council on Environmental Quality
• Office of Management and Budget
• Office of National Drug Control Policy
• Office of Science and Technology Policy
• Office of the United States Trade Representative

Related posts:

1. Open source headlines from the Open Government plans
2. Flagship Initiatives Shine in Open Government Plans
3. Cabinet members brief Amercan citizens in Year One videos

Unfortunately, the cost of health care and insurance can be as much as a family annual income depending on the type of work you do. So why do some wait until a health problem requires the most expensive emergency room care to treat it? One reason is the federal law. In 1996, the Personal Responsibility and Work Opportunity Reconciliation Act of 1996 (PRWORA) sought to reduce federal spending. This law has had the opposite effect.

Some who are uncertain of their immigration status do not apply for benefits because they are afraid.

Under this legislation, undocumented immigrants became ineligible for Medicaid and other federally-funded social services, and only eligible for emergency medical assistance. The Act also requires that all state and federal welfare agencies report any illegal immigrants who apply for benefits to the Immigration and Naturalization Service (now the Department of Homeland Security) unless it’s health care delivered in the emergency room.

Emergency Medicaid is predominantly a program for childbirth coverage, although use and spending are shifting toward non-pregnant adults, particularly those who are elderly and disabled. Whether or not a person is eligible for Medicaid will depend on the State where he or she lives. Medicaid spending for emergency care, of recent and undocumented immigrants (although a small proportion of the total Medicaid budget) is increasing in some states. While states are not required to identify or report their Medicaid expenditures specific to undocumented aliens, some states do provide data suggesting that most of their emergency Medicaid expenditures were for services provided to undocumented aliens.

According an article in the Journal of the American Medical Association, treatment of unauthorized immigrants contributes to uncompensated care costs, but the main reason such costs are increasing is the rise in the number of people who lack health insurance. Immigrants represent only about 20% of the uninsured.

We now have a growing, uninsured, aging population. We need a better alternative to our current system because in the end, we are all paying for this expensive emergency room care. Here are a few suggestions.

• Reduce costly healthcare expense by creating legislation that does not direct people to the emergency room
• Encourage the sharing of aggregate, non-confidential provider data to track expense trends
• Consider alternatives to voluntary, ad hoc state reports in guiding national health policy
• Focus on reducing government expense and not enforcement in the healthcare setting

Related posts:

1. HHS launches Healthcare.gov
2. Immigration detention by the numbers
3. HITECH Act and government access to private health records

Why is Drupal important to the the Federal government? That is the main topic I will cover in a 3-part series here on GovFresh. I’ll start with some high-profile examples of who is using Drupal effectively in government and why Drupal is a great fit for what these sites are trying to achieve. My second post will focus on the unique aspects of providing web content management for government that are relevant for Drupal (i.e. what can Drupal learn from Government?). My final post will provide ideas and predictions for the future of Drupal within the Federal government.

Who is using Drupal effectively now at the federal level? Not as many agencies as we’d like. While open source provides a great return on investment for Federal CIOs under budgetary pressure, open source adoption on U.S. government websites has not yet hit critical mass. I believe this will change in 2010 due in no small part to the success of early adopters in demonstrating cost savings, time to market and features critical to government to citizen outreach. So while growing in popularity with CIOs, it is New Media Directors that have found the tool most useful because of its ease of implementation and flexibility to extend sites to include the best of social media, user participation and collaboration and data integration.

Here are five sites using Drupal effectively to achieve the objectives of the open government directive and promoting the use of open concepts to improve the business of government.

Recovery at Commerce

The Department of Commerce loves Drupal, and for good reason: a site like this can be developed and launched quickly and inexpensively. Being on the front lines of the economic recovery efforts, Commerce has a lot to share with the public and good reason to do that quickly and efficiently. Unlike its better known federal-wide parent site, Recovery.gov, this agency transparency initiative is still running on Drupal. Regrettably, Recovery.gov which was running on Drupal was replaced by SharePoint when a re-compete to the contract famously switched platforms and vendors. It will probably be known to Drupalers as “the one that got away” for a while to come. The Commerce department’s recovery site makes use of Drupal’s ease of integration with mashups. Data and reports are easy to find and download in original .xls formats and I can get an RSS feed of major communications and activities. While still a fairly simple site, it’s simplicity makes it accessible and easy for the common citizen to find what they are looking for. It is easy to see how this site could blossom into a model destination for Commerce communications, collaboration and participation on all things recovery.

Federal IT Spending Dashboard

Launched in July of last year by Vivek Kundra, the Federal Chief Information Officer, the dashboard was created to allow CIOs of various government agencies to show the effectiveness with which they have managed government IT spending. As such, this site has been featured very prominently as an open gov example for its transparency, its use of open data and a very strong sense of government accountability. Kundra explains the site as a place that “… allows you to see what IT projects are working and on-schedule (and which are not), offer alternative approaches, and provide direct feedback to the chief information officers at federal agencies – in effect, keeping tabs on the people who are responsible for taxpayer dollars for technology.” Ultimately, that hits on all three tenets of the directive and does it in a visually appealing and useful way that does not get the user bogged down in text. The graphing techniques are unique and unconventional like the budget year tree map (well okay that one still confuses me a bit, but it still proves that transparency can be fun to browse and explore).

Federal Labor Relations Authority

This is a simple, effective example of a government site that can be easily stood up with Drupal. It is a great example of how government agency sites don’t have to be overly complex to achieve their mission. The FLRA is an independent administrative federal agency. As such, the FLRA mission is fairly straight forward: carry out five (5) primary statutory responsibilities as efficiently as possible. This site provides good direction on what the agency does and how the agency can help a citizen worker. What caught my attention is that it promotes the /open aspect of the open government directive (OGD) prominently on its homepage (though technically I believe the FLRA would be exempt from this requirement) and links to 3 (albeit incredibly light) data sets in XML format. This is what the OGD is asking all cabinet level agencies do and someone here read the memo.

Data.gov.uk

This new UK government site is a shining example of the merger of open source, open data and the semantic web. This is my second favorite government site running on Drupal. It illustrates that Europe has a lot to teach us about open government. The site is the product of Sir Tim Berners-Lee (most notably the guy who created the World Wide Web) and Professor Nigel Shadbolt as a project for the UK’s efforts to make data more open and accessible on the web. This site is the UK’s answer to our data.gov project. Reportedly they selected Drupal for both its flexibility as a CMS and its native integration with semantic web concepts and technology. With an Apps download section, idea galleries, forums, a blog, a wiki, and the ability to search, browse and query against the data sets, this was done in the spirit of try it all and see what sticks. I admire the pragmatic goals of the site.

The White House

Currently a shining star of Drupal in government, the conversion of this site in October of last year sparked a lively and interesting debate on the use of open source in government (Disclaimer: my firm was the developer on this effort) While it served to squelch much of the criticism over the scalability and performance of Drupal as a platform for very high traffic sites, it also forced people to question whether the security of open source was ready for prime time. Many critics cited the openness and availability of open source code to be a weakness, while others claimed it as a benefit. Tim O’Reilly’s post did a good job of refocusing the discussion to the benefits of choosing Drupal for the White House site:

“More than just security, though, the White House saw the opportunity to increase their flexibility. Drupal has a huge library of user-contributed modules that will provide functionality the White House can use to expand its social media capabilities, with everything from super-scalable live chats to multi-lingual support. In many ways, this is the complement to the Government as Platform mantra I’ve been chanting in Washington.”

In addition to these attributes, the site features a robust blog, multimedia delivery and is the home to many micro-sites that can be quickly stood up to address various initiatives, councils and committees that fall under the purview of the Administration, including the king of all /open sites, whitehouse.gov/open, home to the open government directive itself.

There are many great examples of Drupal use for the betterment and opening of government. For more about the use of Drupal in government, stay tuned for my next post. Also, for those interested in a more comprehensive list of known government sites using Drupal both in the U.S. and at large throughout the world, check out the Drupal in Government group on Drupal.org.

Related posts:

1. A new model for public sector open source adoption using Drupal
2. White House announces ‘Open Government Directive’
3. Drupal: The New Gov 2.0 Site Builder?

What do you think? Which are most informative? Authentic? Is this an effective way to familiarize citizens to public servants and put a face on government?

Secretary Robert Gates, Department of Defense:

Secretary Steven Chu, Department of Energy:

Secretary Ray LaHood, Department of Transportation:

Secretary Thomas J. Vilsack, Department of Agriculture:

Secretary Hillary Rodham Clinton, Department of State:

Administrator Lisa P. Jackson, Environmental Protection Agency:

Secretary Timothy F. Geithner, Department of Treasury:

Secretary Janet A. Napolitano, Department of Homeland Security:

Secretary Gary F. Locke, Department of Commerce:

Secretary Hilda L. Solis, Department of Labor:

Secretary Kathleen Sebelius, Department of Health and Human Services:

Secretary Kenneth L. Salazar, Department of the Interior:

Ambassador Ronald Kirk, United States Trade Representative:

Ambassador Susan Rice, United States Ambassador to the United Nations:

Director Peter R. Orszag, Office of Management & Budget:

Attorney General Eric Holder, Department of Justice:

Secretary Eric K. Shinseki, Department of Veterans Affairs:

Chair Christina Romer, Council of Economic Advisers:

Secretary Arne Duncan, Department of Education:

Related posts:

1. Quick links: Federal agency open government plans
2. New year, new Manor innovations
3. Citizens out in force with CitySourced

Recently, Dr. John Clarke’s H1N1 Rap won the flu prevention video contest sponsored by the Department of Health & Human Services:

Dr. Clarke’s innovative approach using social media to spread an important message got me thinking:

“Gov 2.0 needs a video.”

In an effort to inspire creative govies, Gov 2.0 enthusiasts, civic songwriters, comedians, poets and musicians, GovFresh is sponsoring a ‘Best Gov 2.0 Video’ contest.

Details

Prize:

• ‘Above the fold’ home page feature on GovFresh.com and GovFresh.tv through December 31, 2009.
• Awesome GovLoop t-shirt.
• Bragging rights at every Gov 2.0 event under the sun.
• If you would like to sponsor a prize, please share in comments or send us a message, and we’ll add to the list.

Rules:

• Must be creative.
• Must be original, specifically for this contest.

Dates:

• October 31, 2009: Deadline
• Nov 1-7, 2009: Voting
• Nov 8, 2009: Winner announced

Who’s first?

Related posts:

1. USA.gov offers $2500 for best video
2. Digital Democracy Contest aims to ‘Empower students to engage 21st Century government’
3. CDC’s social media efforts featured in Advertising Age video

“Using Gov 2.0 to Enable Better Engagement and Reduce Burden on Farmers” video interview with a U.S. Department of Agriculture representative from the Microsoft Public Sector CIO Summit 2009.

He discusses how the agency is trying to get a consensus on what Gov 2.0 is, citizen engagement, the importance of broadband in connecting with farmers, how they collaborate (teleconferences, face-to-face meetings, CoLab) and USDA’s approach to social media usage, from individual teams to the agency-level, especially Twitter and Facebook.

USDA Twitter accounts:

• @USDAFoodSafety
• @usda_nass

Related posts:

1. Spacebook lead Emma Antunes talks social media, collaboration
2. Social media in government is like riding a bike
3. Video: Salt Lake Valley Health Department shares H1N1 social media efforts