The Engineering Perspective
Return to: Care Plan Project page
Return to: Types of Plan - Differentiation and Definitions page
The problems software try to solve often involve elements of inescapable complexity. The complexity is compounded by changing or even fuzzy requirements. the task of software engineers often involves engineering the illusion of simplicity. One strategy to achieve "simplicity" is only to represent concepts as different entities/classes when differentiating characteristics (as attributes and behaviours) can be identified.
When designing Care Plan from engineering perspective, it is desirable to create a single structure/model capable of supporting the instantiation of different types of plans (care plan, plan of care, treatment plan).
The Patient Care Domain Analysis Model (DAM) includes a conceptual and a logical information model representing the structure of the generic PLAN concept:
- Care Plan Model Wiki page: http://wiki.hl7.org/index.php?title=Care_Plan
The logical model is designed to support the instantiation of different types of plan. The model:
- - includes attributes and behaviours that allows the differentiation of the different types of plan
- - is capable of supporting various use cases defined by the user community. This capability is demonstrated by a number of logical walkthrough of the model using the different clinical storyboards and use cases developed by the Care Plan project team
