Develop Solution Requirements

Requirements, broadly defined, are a list of criteria, specifications, and/or functional needs that a technology platform or vendor would ideally fulfill. We often re-frame these requirements as vendor-facing questions to support information gathering in the vetting process. Consider meeting with the pilot metrics consultant to understand how your metrics might align with your requirements.


  1. Before defining requirements, it is important to understand (or, in some cases, create) your organization’s process for selecting a technology solution. This may involve working closely with leaders from a variety of departments like legal, purchasing, compliance, as well as strategic leaders.
  2. Develop and document a set of business, functional, and technical requirements that are “must haves” and “nice to haves.” Examples of requirements to consider might include: EHR integration, languages available, literacy level, geographic coverage, target populations, role-based interfaces (e.g MA v. MD), reporting capability, security assessment, service level agreements.