Requirements These requirements are the fundamental needs that are met by the model, derived from the supplied use cases Provide a way to indicate which things are of concern. The Health Concern concept allows people to indicate which facts are actually of concern (e.g., a for physicians) and should be evident to care providers and other care “Problem List” team members. Support different and persons’ roles’ perspectives. Different users will have different needs and expectations regarding what is actually of concern. Maintain a traceable record of a concern, for understanding, as the concern evolves. As providers investigate health issues, their understanding of the underlying problem often changes. However, it is sometimes important to be able to understand that diagnosis today’s is the same problem that initially presented as something else--pneumonia as the flu, or gastritis as chest pain. This ability is especially important when reconciling data across organizations. Associate events with concerns in order to provide a consolidated view of a concern. The ability to assign specific data to a concern will allow a user to see the information associated with a concern without having to sort through extraneous data. Some systems may be able to perform these assignments by rule (e.g., observations ordered in the context of caring for a particular concern), but the ability to assert a relationship is fundamental. We also observe some implications of this concept. Health concerns can be created by different persons in different systems without knowing about each other. Therefore, the ability to aggregate and reconcile concerns is desirable, although the concerns of one person may differ in relevance, granularity, or certainty compared to those of another. Ownership of a health concern is often a policy matter within an institution.
Requirements These requirements are the fundamental needs that are met by the model, derived from the supplied use cases Provide a way to indicate which things are of concern. The Health Concern concept allows people to indicate which facts are actually of concern (e.g., a “Problem List” for physicians) and should be evident to care providers and other care team members. Support different persons’ and roles’ perspectives. Different users will have different needs and expectations regarding what is actually of concern. Maintain a traceable record of a concern, for understanding, as the concern evolves. As providers investigate health issues, their understanding of the underlying problem often changes. However, it is sometimes important to be able to understand that today’s diagnosis is the same problem that initially presented as something else--pneumonia as the flu, or gastritis as chest pain. This ability is especially important when reconciling data across organizations. Associate events with concerns in order to provide a consolidated view of a concern. The ability to assign specific data to a concern will allow a user to see the information associated with a concern without having to sort through extraneous data. Some systems may be able to perform these assignments by rule (e.g., observations ordered in the context of caring for a particular concern), but the ability to assert a relationship is fundamental. We also observe some implications of this concept. Health concerns can be created by different persons in different systems without knowing about each other. Therefore, the ability to aggregate and reconcile concerns is desirable, although the concerns of one person may differ in relevance, granularity, or certainty compared to those of another. Ownership of a health concern is often a policy matter within an institution.
HealthConcernDAM20160316.docx