Ensuring Sufficient Breadth in Use Case Development: How Should Non-functional Requirements Be Elicited and Represented?

Requirements informed by clinical context are needed to drive the development of emerging medical device communications interoperability standards and practices. Efforts thus far have focused on working with clinical engineers and clinicians to elicit functional requirements. We provide rationale to extend the effort to include eliciting nonfunctional requirements from the provider community, suggest methods to be explored, and identify issues germane to the realization of standards-based interoperability that this work may inform.