Health Data Platform Metadata Challenge

Submission Deadline

Submissions are Closed

Contact

Hemali Thakkar

Prizes

  • First Place: $20,000 plus conference exhibition opportunity
  • Second Place: $10,000
  • Third Place: $5,000

First Place

Tetherless World Constellation

Tetherless World Constellation logo

Team Members

James McCusker, Timothy Lebo, Alvaro Graves, Kristine Gloria, John Erickson

We present a set of in-house developed tools which enable the discovery of, access to, and integration of the Health and Human Services' datasets. Over the past several years, TWC has built many of the tools, has set the standards, and has engineered the architecture of the Web that many of us use today. We mirrored the hub.healthdata.gov CKAN instance using its API to our own instance at healthdata.tw.rpi.edu/hub. This allowed us to both improve the CKAN-based metadata, including adding Data Dictionaries and Technical Documentation as Resources, and to improve the RDF generated by CKAN.

Second Place

NCBO

NCBO logo

Team Members

Natasha Noy, Csongor Nyulas, Manuel Salvadores, Amy Isabella Sentis, Mark Musen

We use semantic web technologies to represent three levels of metadata about the healthdata.gov datasets: (1) descriptions of the datasets themselves; (2) descriptions of the content structure in the dataset; and (3) controlled vocabularies derived from standard terminologies that represent the value sets for dataset components. The NCBO BioPortal serves an open repository for the value sets in the datasets and provides detailed information, resolvable URIs and both Web service and RDF access to all controlled vocabularies that we use in our solution.

Third Place

HealthLink

HealthLink logo

Team Members

Chintan Patel

We have created HealthLink - a set of ontologies to link several datasets from HealthData.gov. We examined all the 370+ datasets in HealthData.gov and identified those providing CSV data files. We created 10 different ontologies in protege creating concepts as needed to link datasets and re-using concepts from existing ontologies such as foaf.

Background


We apologize for the inconvenience, but due to technical issues the audio and video unfortunately do not correspond to video.

As part of the HHS Open Government Plan, the HealthData.gov Platform (HDP) is a flagship initiative and focal point helping to establish learning communities that collaboratively evolve and mature the utility and usability of a broad range of health and human service data. HDP is leveraging Web oriented and Cloud based architecture frameworks and standards, running on open source software components to deliver enhanced Health IT infrastructure capabilities. HDP will facilitate better integration, analysis, and interpretation of our data, helping meet the growing demand for more public and private sector value added information services. Through expanded use of application programming interfaces (APIs) and the incorporation of new data element identification and metadata tagging methodologies, HDP will improve the liquidity of health data, increasing the efficiency of data transfer and the effectiveness of data distributions. Overall, HDP will deliver greater potential for new data driven insights into complex interactions of health and health care services.

To augment the HDP effort, seven complementary challenges, to be released over the course of a year, will encourage innovation around initial platform- and domain-specific priority areas, fostering opportunities to tap the creativity of entrepreneurs and productivity of developers. The challenge competitions are of two types: three domain-specific challenges are intended to improve the integration and liquidity of data made available, and four platform-specific challenges are intended to enhance the capabilities of the technology components being employed. The virtual machines and codebase outputs from innovations demonstrated by challenge participants will be made publically available through HHS Github repositories (see https://github.com/hhs/) as release candidates for further community refinement as necessary, including open source licensing and contributor attribution as appropriate, with the goal being incorporation into subsequent HDP product roadmap releases.

The “Health Data Platform Metadata Challenge” requests the application of existing voluntary consensus standards for metadata common to all open government data, and invites new designs for health domain specific metadata to classify datasets in our growing catalog, creating entities, attributes and relations that form the foundations for better discovery, integration and liquidity.

Description

The W3C has a number of standard vocabulary recommendations for Linked Data publishers, defining cross domain semantic metadata of open government data, including concept schemes , provenance , statistics , organizations , people , data catalogs and their holdings , linked data assets , and geospatial data, in addition to the foundational standards of the Web of Data (such as HTTP, XML, RDF and various serializations, SPARQL, OWL, etc). Other voluntary consensus standards development organizations are also making valuable contributions to open standards for Linked Data publishers, such as the emerging GeoSPARQL standard from the Open Geospatial Consortium .

In some cases, the entities and relations in these vocabulary standards are expressed using UML class diagrams as an abstract syntax, then automatically translated into various concrete syntaxes like XML Schemas and RDF Schemas , which also makes many of the standards from the Object Management Group easy to express as RDF Schemas, such as those that describe business motivation (including but not limited to vision, mission, strategies, tactics, goals, objectives), service orientation , process automation , systems integration , and other government specific standards . Oftentimes there exist domain specific standards organizations, with standards products that express domain specific entities and relations, such as those for the health or environmental sectors . The Data.gov PMO has recently stood up a site to collect these standards when expressed as RDF Schemas for use by the growing community of Government Linked Data publishers, which includes HHS/CMS, EPA, DOE/NREL, USDA, and the Library of Congress.

The challenge winner will demonstrate the application of voluntary consensus and de facto cross domain and domain specific standards, using as many of the HHS datasets available on healthdata.gov as possible. There are two objectives:

  1. Apply existing standards as RDF Schemas from voluntary consensus standards organizations (W3C, OMG, OGC, etc.) for expressing cross domain metadata that is common to all open government data.
  2. Design new HHS domain specific metadata based on the data made available on healthdata.gov where no RDF Schema is otherwise given or available.

When designing new metadata expressed as RDF Schemas, designers should:

  • Leverage existing data dictionaries expressed as natural language in the creation of new conceptual schemas, as provided by domain authorities;
  • Observe best practices for URI’s schemes that is consistent with existing healthdata.gov work (such as the Clinical Quality Linked Data release from HDI 2011); and
  • Organize related concepts into small, compose-able component vocabularies.

Turtle syntax for RDFS and RDF is preferred. The contributed code will be given an open source license and managed by HHS on github.com, with copyright and attribution to the developer(s) as appropriate, and will ideally be used to populate vocab.data.gov.

Timeline

  • Submission Period Begins: June 5, 2012
  • Submission Period for Entries Ends: January 6, 2013
  • Evaluation Process for Entries Begins: January 8, 2013
  • Evaluation Process for Entries Ends: January 15, 2013
  • Winners notified: January 28, 2013
  • Winners Announced: Industry conference TBD

Evaluation Criteria

The ONC review panel will make selections based upon the following criteria:

  • Metadata (15%): the number of cross domain and domain specific voluntary consensus and defacto standard schemas, vocabularies or ontologies that are (re)used or designed and applied to HHS data on healthdata.gov
  • Data (15%): the number of datasets that the standards based cross domain metadata and schema designed domain specific data is applied to
  • Linked Data (15%): the solution should use best practices for the expression of metadata definitions and instance data identification, leveraging the relevant open standards, including but not limited to foundational standards (RDF, RDFS, SPARQL, OWL), and other defacto vocabularies and ontologies such as those listed here as required, with the expectation that existing standards will be reused to the fullest extent possible.
  • Components (15%): leveraging software components that are already a part of the HDP is preferable, but other open source solutions may be used
  • Tools (15%): use of automation and round trip engineering that enable multiple concrete syntax realization from abstract syntax of cross domain and/or domain specific metadata is desirable, with no expectation that the tools must be open source or otherwise contributed to HDP as part of this challenge submission. Only newly designed domain specific RDF Schemas, their composition cross domain standards based RDF Schemas, and their application to various datasets are expected to be submitted for this challenge. Tool functionality may be highlighted to explain implementations as desired.
  • Best practices (15%): where any new schemas and software code is created, they should exemplify design best practices and known software patterns, or otherwise establish them.
  • Documentation (5%): articulation of design using well known architecture artifacts
  • Engagement (5%): willingness to participate in the community as a maintainer/committer after award

Submission Requirements

In order for an entry to be eligible to win this Challenge, it must meet the following requirements:

  1. No ONC logo – The app must not use ONC’s logo or official seal in the Submission, and must not claim endorsement.
  2. Functionality/Accuracy – A Submission may be disqualified if the software application fails to function as expressed in the description provided by the user, or if the software application provides inaccurate or incomplete information.
  3. Security – Submissions must be free of malware. Contestant agrees that the ONC may conduct testing on the app to determine whether malware or other security threats may be present. ONC may disqualify the app if, in ONC’s judgment, the app may damage government or others’ equipment or operating environment.

Terms & Conditions

OFFICIAL RULES

NO PURCHASE OR PAYMENT NECESSARY TO ENTER OR TO WIN.  A PURCHASE WILL NOT IMPROVE YOUR CHANCES OF WINNING.  VOID WHERE PROHIBITED.

SPONSOR:  US Department of Health and Human Services, the Office of the National Coordinator for Health IT ("Sponsor").

ADMINISTRATOR:  The administrator of the Challenge is Health 2.0, LLC, 650 Delancey St, #221, San Francisco, CA 94107 ("Administrator")

CHALLENGE DESCRIPTION:  The Challenge begins at 10:00 AM Eastern Time on Tuesday, June 5, 2012 and ends at 11:59 PM Eastern Time on Sunday, January 6, 2013 ("Challenge Period"). The “Health Data Platform Metadata Challenge” requests the application of existing voluntary consensus standards for metadata common to all open government data, and invites new designs for health domain specific metadata to classify datasets in our growing catalog, creating entities, attributes and relations that form the foundations for better discovery, integration and liquidity. The teams that submit the winning applications will win: 1.) First Place - $20,000 and a demo opportunity, 2.) Second Place - $10,000 and 3.) Third Pace - $5,000.  Entry into the Challenge does not constitute entry into any other challenge or promotion, including, without limitation, other similar challenges or promotions offered by Sponsor and/or Administrator.  By participating in the Challenge, each entrant unconditionally accepts and agrees to comply with and abide by these Official Rules and the decisions of Sponsor, Administrator, and/or the individual advisors, which shall be final and binding in all respects.

ELIGIBILITY:  To be eligible to win a prize under this challenge, an individual or entity: (a) Shall have registered to participate in the competition under the rules promulgated by the Office of the National Coordinator for Health Information Technology; (b) Shall have complied with all the requirements under this section; (c)  In the case of a private entity, shall be incorporated in and maintain a primary place of business in the United States, and in the case of an individual, participating in a group, shall be a citizen or permanent resident of the United States and 18 years old or older as of the time of entry; and (d) May not be a Federal entity or Federal employee acting within the scope of their employment.  An individual or entity shall not be deemed ineligible because the individual or entity used Federal facilities or consulted with Federal employees during a competition if the facilities and employees are made available to all individuals and entities participating in the competition on an equitable basis.  Employees of Sponsor, Administrator, each of their affiliates, and/or any other individual or entity associated with the development, evaluation, or administration of the Challenge as well as members of such persons' immediate families (spouses, children, siblings, parents), and persons living in the same household as such persons, whether or not related, are not eligible to participate in the Challenge.

HOW TO ENTER:  To enter:  (a) The challenge winner will demonstrate the application of voluntary consensus and de facto cross domain and domain specific standards, using as many of the HHS datasets available on healthdata.gov as possible. There are two objectives:

  1. Apply existing standards as RDF Schemas from voluntary consensus standards organizations (W3C, OMG, OGC, etc.) for expressing cross domain metadata that is common to all open government data.
  2. Design new HHS domain specific metadata based on the data made available on healthdata.gov where no RDF Schema is otherwise given or available.

 ("Submission"); (b) go to the website located at www.health2challenge.org (the "Challenge Website"), complete the Official Registration Form to officially register for the competition; (c) prior to the submission deadline you will receive additional instructions to submit your entry, a video demonstrating the Submission's capabilities and functionality, and an electronic slide presentation describing the submission according to the instructions posted on the Challenge Website.  You may only enter as part of a team.  Teams must include no less than two (2) people and each team member must be clearly identified on the team's Official Entry Form to be eligible.  All participants are required to provide written consent to the rules upon or before submitting an entry.  Submissions must be received during the Challenge Period to be eligible.  Administrator is the official timekeeper for the Challenge.  No substitutions of new versions of Submissions will be accepted under any circumstances once the original Submission is submitted for consideration.  In the event of a dispute regarding the identity of the individual or team who actually submitted the entry cannot be resolved to Sponsor's and/or Administrator's satisfaction, the affected entry will be deemed ineligible.  Except as otherwise stated in these Official Rules, personal information collected in connection with the Challenge will be used by Sponsor in accordance with Sponsor's privacy policy and by Administrator in accordance with Administrator's privacy policy available on the Website and with any additional consent given by an entrant at the time of entry.  All entry information and materials, including any copy of the Submission submitted to Sponsor, become the property of Sponsor and will not be acknowledged or returned.  Proof of submission is not considered proof of delivery to or receipt of such entry.  Furthermore, Sponsor and Administrator shall have no liability for any Submission that is lost, intercepted, or not received by Sponsor and/or Administrator.  Sponsor and Administrator assume no liability or responsibility for any error, omission, interruption, deletion, theft, or destruction or unauthorized access to, or alteration of, Submissions.

REPRESENTATIONS AND WARRANTIES/INDEMNIFICATION:  By participating in the Challenge, each entrant represents, warrants, and covenants as follows: (a) entrant is the sole author, creator, and owner of the Submission; (b) the Submission is not the subject of any actual or threatened litigation or claim; (c) the Submission does not and will not violate or infringe upon the intellectual property rights, privacy rights, publicity rights, or other legal rights of any third party; (d) the Submission does not and will not contain any harmful computer code (sometimes referred to as "malware," "viruses" or "worms"); and (e) the Submission, and entrants use of the Submission, does not and will not violate any applicable laws or regulations, including, without limitation, applicable export control laws and regulations of the U.S. and other jurisdictions.  If the Submission includes any third party works (such as third party content or open source code), entrant must be able to provide, upon Sponsor and/or Administrator's request, all appropriate licenses and releases for such third party works.  In the event entrant cannot provide all required licenses and releases, Sponsor reserves the right, in Sponsor's sole discretion, to disqualify the applicable Submission, or seek to secure the licenses and releases for Sponsor's benefit and allow the applicable Submission to remain in the Challenge.  Entrants will indemnify, defend, and hold harmless Sponsor and Administrator from and against all third party claims, actions, or proceedings of any kind and from any and all damages, liabilities, costs, and expenses relating to or arising from entrant's Submission or any breach or alleged breach of any of the representations, warranties, and covenants of entrant hereunder.  Sponsor and/or Administrator reserves the right to disqualify any Submission that Sponsor and/or Administrator, in its sole discretion, deems to violate these Official Rules.

SUBMISSION LICENSE:  The virtual machines and codebase outputs from innovations demonstrated by challenge participants will be made publically available through HHS Github repositories (see https://github.com/hhs/) as release candidates for further community refinement as necessary, with the goal being incorporation into subsequent HDP product roadmap releases. The contributed code will be given an open source license, with copyright and attribution to the developer(s) as appropriate, and will ideally be used to populate vocab.data.gov.

PUBLICITY RELEASE:  By participating in the Challenge, in addition to any other grants granted herein or which may be granted in any other agreement entered into between Sponsor and/or Administrator, on the one hand, and any entrant in the Challenge, on the other hand, each entrant hereby irrevocably (a) grants to Sponsor and Administrator the right to use such entrant's name, likeness, image, and biographical information in any and all media for any purpose, including, without limitation, advertising and promotional purposes relating to the Challenge and (b) releases Sponsor and Administrator from any liability with respect thereto.

U.S. GOVERNMENT SUPPORT, RIGHTS, AND WAIVER:   Sponsor and Administrator are administering the Challenge with the support of the U.S. Department of Health & Human Services pursuant to the American COMPETES Reauthorization Act (the "Act").  Subsection (j) of section 24 of the Act establishes that the Government is prohibited from acquiring an interest in intellectual property developed by a participant in a prize competition, such as the Challenge, without the written consent of the participant.  Registered participants shall be required to agree to assume any and all risks and waive claims against the Federal Government and its related entities, except in the case of willful misconduct, for any injury, death, damage, or loss of property, revenue, or profits, whether direct, indirect, or consequential, arising from their participation in a competition, whether the injury, death, damage, or loss arises through negligence or otherwise. Participants shall be required to obtain liability insurance or demonstrate financial responsibility, in amounts determined by the head of the Office of the National Coordinator for Health Information Technology, for claims by (a) a third party for death, bodily injury, or property damage, or loss resulting from an activity carried out in connection with participation in a competition, with the Federal Government named as an additional insured under the registered participant's insurance policy and registered participants agreeing to indemnify the Federal Government against third party claims for damages arising from or related to competition activities; and (b) the Federal Government for damage or loss to Government property resulting from such an activity.

WINNER SELECTION/EVALUATION CRITERIA:  The ONC review panel will make selections based upon the following criteria:

  • Metadata: the number of cross domain and domain specific voluntary consensus and defacto standard schemas, vocabularies or ontologies that are (re)used or designed and applied to HHS data on healthdata.gov
  • Data: the number of datasets that the standards based cross domain metadata and schema designed domain specific data is applied to
  • Linked Data: the solution should use best practices for the expression of metadata definitions and instance data identification, leveraging the relevant open standards, including but not limited to foundational standards (RDF, RDFS, SPARQL, OWL), and other defacto vocabularies and ontologies such as those listed here as required, with the expectation that existing standards will be reused to the fullest extent possible.
  • Components: leveraging software components that are already a part of the HDP is preferable, but other open source solutions may be used
  • Tools: use of automation and round trip engineering that enable multiple concrete syntax realization from abstract syntax of cross domain and/or domain specific metadata is desirable, with no expectation that the tools must be open source or otherwise contributed to HDP as part of this challenge submission. Only newly designed domain specific RDF Schemas, their composition cross domain standards based RDF Schemas, and their application to various datasets are expected to be submitted for this challenge. Tool functionality may be highlighted to explain implementations as desired.
  • Best practices: where any new schemas and software code is created, they should exemplify design best practices and known software patterns, or otherwise establish them.
  • Documentation: articulation of design using well known architecture artifacts

The evaluation criteria are to be applied in the sole discretion of Sponsor and the individual advisors.  By participating in the Challenge, each entrant into the Challenge acknowledges and agrees that such evaluations may differ from person to person and agrees to be bound by and not challenge the final decisions of Sponsor and the individual advisors.

NOTICE TO WINNERS:  Attempts to notify potential winners will be made using the contact information provided on the winner's Official Entry Form.  Sponsor and Administrator are not responsible for e-mail or other communication problems of any kind.  If, despite reasonable efforts, a potential winner does not respond within five (5) days of the first notification attempt (or a shorter time as exigencies may require), or if the prize or prize notification is returned as unclaimed or undeliverable to such potential winner, such potential winner will forfeit his or her prize and an alternate winner may be selected.  If any potential prize winner is found to be ineligible, or if he or she has not complied with these Official Rules or declines the applicable prize for any reason prior to award, such potential prize winner will be disqualified and an alternate winner may be selected.  Sponsor may successively attempt to contact up to two (2) potential prize winners in accordance with such procedure, and if there is still no confirmed prize winner after such attempts have been made, if any, the applicable prize may go unawarded.

ANTICIPATED NUMBER OF ENTRANTS:  Many will enter, three winning submissions will be selected.  Actual odds of winning depend on the number of eligible entries received.  Sponsor and Administrator cannot accurately predict the number of entrants who will participate in the Challenge. 

PRIZES:  The winning teams will receive: 1.) First Place - $20,000 and a demo opportunity 2.) Second Place - $15,000 and 3.) Third Pace - $5,000.

GENERAL PRIZE CONDITIONS:  The potential winner may be required to execute an Affidavit of Eligibility, a Liability Release and (where imposing such condition is legal) a Publicity Release (collectively "Prize Claim Documents).  If a winner fails or refuses to sign and return all Prize Claim Documents within five (5) days of Sponsor's and/or Administrator's request (or a shorter time as exigencies may require), the winner may be disqualified and an alternate winner may be selected.  No more than the advertised number of prizes will be awarded.  Prizes will be delivered only to an address in the U.S.  No cash alternative or substitution or transfer of prizes will be allowed, except Sponsor reserves the right in its sole discretion to substitute prizes of comparable value, in whole or in part, for any reason.  THE WINNER IS RESPONSIBLE FOR REPORTING AND PAYING ANY INCOME TAXES OR OTHER TAXES THAT MAY APPLY TO ACCEPTING A PRIZE; SPONSOR AND ADMINISTRATOR ARE NOT RESPONSIBLE FOR AND WILL NOT PAY ANY SUCH TAXES.

DATES/DEADLINES:  Because of the unique nature and scope of the Challenge, Sponsor and Administrator reserve the right, in addition to those other rights reserved herein, to modify any dates or deadlines set forth in these Official Rules or otherwise governing the Challenge.

GENERAL LIABILITY RELEASE/FORCE MAJEURE:  Each entrant agrees that Sponsor and Administrator (a) shall not be responsible or liable for any losses, damages, or injuries of any kind (including death) resulting from participation in the Challenge or any Challenge-related activity, or from entrants' acceptance, receipt, possession, use, or misuse of any prize, and (b) have not made any warranty, representation, or guarantee, express or implied, in fact or in law, with respect to any prize, including, without limitation, regarding such prize's merchantability or fitness for a particular purpose.  Entrants will indemnify, defend, and hold harmless Sponsor and Administrator from and against all third party claims, actions, or proceedings of any kind and from any and all damages, liabilities, costs, and expenses relating to or arising from entrant's participation in the Challenge.  Sponsor and Administrator assumes no responsibility for any damage to an entrant's computer system which is occasioned by accessing the Website or other Challenge-related websites or participating in the Challenge, or for any computer system, phone line, hardware, software, or program malfunctions, or other errors, failures, delayed computer transmissions, or network connections that are human or technical in nature.  Without limiting the generality of the foregoing, Sponsor and Administrator are not responsible for incomplete, illegible, misdirected, misprinted, late, lost, postage-due, damaged, or stolen entries or prize notifications; or for lost, interrupted, inaccessible, or unavailable networks, servers, satellites, Internet Service Providers, websites, or other connections; or for miscommunications, failed, jumbled, scrambled, delayed, or misdirected computer, telephone, cable transmissions or other communications; or for any technical malfunctions, failures, difficulties, or other errors of any kind or nature; or for the incorrect or inaccurate capture of information, or the failure to capture any information.  Sponsor and Administrator each reserve the right in their sole discretion to disqualify any individual who is found to be tampering with the entry process or the operation of the Challenge or Website or other Challenge-related websites, to be acting in violation of these Official Rules, or to be acting in an unsportsmanlike or disruptive manner, or with the intent to disrupt or undermine the legitimate operation of the Challenge, or to annoy, abuse, threaten, or harass any other person, and Sponsor and Administrator each reserve the right to seek damages and other remedies from any such person to the fullest extent permitted by law.  In the event an insufficient number of eligible entries are received or Sponsor and/or Administrator is prevented from awarding the prize or continuing with the Challenge as contemplated herein by any event beyond its control, including, without limitation, fire, flood, natural or man-made epidemic, earthquake, explosion, labor dispute or strike, act of God or public enemy, satellite or equipment failure, riot or civil disturbance, terrorist threat or activity, war (declared or undeclared) or any federal state or local government law, order, or regulation, public health crisis, order of any court or jurisdiction, or other cause not reasonably within Sponsor's control ("Force Majeure"), Sponsor and/or Administrator shall have the right to modify, suspend, or terminate the Challenge.  If the Challenge is terminated for Force Majeure before expiration of the Challenge Period, Sponsor and/or Administrator will (if reasonably possible) select a winner from all eligible, non-suspect entries received as of the date of the event giving rise to the termination.  These Official Rules cannot be modified or amended in any way except in a written document issued in accordance with the law by a duly authorized representative of both Sponsor and Administrator.  The invalidity or unenforceability of any provision of these Official Rules shall not affect the validity or enforceability of any other provision.  In the event that any provision is determined to be invalid or otherwise unenforceable or illegal, these Official Rules shall otherwise remain in effect and shall be construed in accordance with their terms as if the invalid or illegal provision were not contained herein.

GOVERNING LAW/JURISDICTION:  All issues and questions concerning the construction, validity, interpretation, and enforceability of these Official Rules or the rights and obligations of entrants, Sponsor and/or Administrator in connection with the Challenge shall be governed by and construed in accordance with the laws of the State of California without giving effect to any choice of law or conflict of laws rules or provisions.  Any legal claims arising from or relating to the Challenge or these Official Rules must be brought in the federal or state courts located in San Francisco, California.

WINNERS LIST/OFFICIAL RULES:  To obtain any legally-required winners list (after the conclusion of the Challenge) or a copy of these Official Rules, send a self-addressed envelope with the proper postage affixed to:  Health 2.0, LLC, Attn: Health 2.0 Developer Challenges, 650 Delancey Street #221, San Francisco, CA 94107.  Please specify "winners list" or "Official Rules" and the name of the specific Challenge in your request.

© 2011 Health 2.0, LLC.  All rights reserved.