Here is what I mean by a ‘dependent obs’:
As you can see, the possible condition types depend on the condition being selected.
Here is a first stab at a design idea for HFE, everything is more than open to be challenged:
<obs id="condition" .. /> <obs dependentObs="condition" dependencySet="MKS:Conditions_Types_Superset" .. />
The dependency set is a superset of sets that operates as a mapping configuration. Each of its sets provides the possible ‘Condition Type’ dependent answers for each ‘Condition’ depended on answer.
It would look as such in a Iniz-like CSV format:
|Same as mapping||Attribute|Referred Concept||Members|
|MKS:Arthropaties_Set||MKS:Arthropaties||MKS:Arthritis; MKS:Arthrosis; MKS:Polyarthritis; MKS:Polyarthrosis; MKS:Coxarthrosis_[arthrosis_of_hip]; MKS:Gonarthrosis_[arthrosis_of_knee]|
|MKS:Dorsalgia_Set||MKS:Dorsalgia||MKS:Cervicalgia; MKS:Sciatica; MKS:Lumbago_with_sciatica; MKS:Low_back_pain|
I would love to get your thoughts on this, 1) about the design and 2) also your insight on the usefulness of/need for such feature.
@angshuonline is there anything as such already available in Bahmni Forms 2.0?