From Demand-Driven Open Data for HHS
For Data Users
- Is it guaranteed that my Use Case will be implemented?
- There's no guarantee that your Use Case will be implemented to your satisfaction. However, as DDOD Administrators, we make every attempt to locate and engage with the relevant Data Owners for your Use Case. All implementation decisions are ultimately made by Data Owners. They typically include a wide range of factors in making their decision, such as cost, risk and relevancy to their organization. But we will ensure that the reasons for any decision are transparent and get published for everyone to see. Often, we also find and document short-term workarounds.
- Can I add to an existing Use Case if my need is slightly different?
- Yes. Adding your requirements to existing Use Cases is encouraged, since the more participants are involved, the more obvious its value becomes. But keep in mind, the Data Owners might decide that your particular requirements are sufficiently different to require a separate implementation. In such cases, your requirements can be relocated to a separate Use Case.
- What kind of Use Cases work well for DDOD?
- Generally, the more specific you can make the requirements the better. Doing so makes it easier for the right Data Owners and identify a solution. If your Use Case is too broad or far reaching, such that an obvious solution cannot be designed or the Data Owner is not obvious, you'll be asked to refine it. Your best bet for understanding the kind of Use Cases that are appropriate, first take a look through the existing ones.
- Will the Use Case implementation be available only to me?
- The implementation and any resulting data is made available to everyone and at the same time. It's unethical for the government to advantage some users over others. By providing your Use Case and collaborating with the Data Owners, you do have the advantage that the implementation is more likely to meet your specific needs. Some Data Owners may make it possible to participate in pre-release testing and validation. But here too, such an opportunity would be made available to anyone who wishes to participate.
- Who can contribute Use Cases?
- Absolutely anyone... It could be groups or individuals in industry, research, media, non-profits, local governments, etc. There's additional benefit in finding others to submit a use case with you. Doing so provides more information about the relative value of the use case.
- How long will it take to implement?
- Every Use Case is unique. In the best case, a use case quickly gets to Data Owners who have resources for quick implementation. But for more complex or obscure cases, it might even take several days just to find the right Data Owners. And implementation could be slowed down by challenges with funding, data sensitivity, and organizational priorities. That said, often we can document short-term workarounds for the Data User.
- Why am I being asked the value of my Use Case?
- Understanding the full value of the Use Case could be an important aspect in the Data Owner's decision on how to prioritize it. We first want you to identify the value to you specifically. For example, how core is it to the operations of your organization or to your research. We also want you to help us understand your perceptions about the possible value to the industry or public health.
- Why is the DDOD website in wiki format?
- The process of working through DDOD Use Cases generates a great deal of information and insights not found anywhere else. The optimal format for managing such a knowledge base while enabling contributions from all parties involved (Data Users, Data Owners, and DDOD Administrators) is a wiki. (See: Why a Wiki?)
- Where can I find the list of existing Use Cases?
- Use Cases are first entered as Github issues here: https://github.com/demand-driven-open-data/ddod-intake/issues. All communications between Data Users and Data Owners should occur as comments under each issue. The detailed description, stated value, specifications and solution for each use case can be found on this wiki: Use Cases