You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Earlier in the projects history it was decided not to use role groups for the Observables model, mainly because at the time, the model was proposed to include nested definitions more specific than what role grouping admits. Also, the nesting patterns using role groups for procedures and findings (i.e. having more than one "part" of the procedure or more than one "condition" for the finding) does not apply to observables. There will only ever be one kind of quality and observation procedure referred to by one observable.

Below is an example of the relationship table for an observable created using SnoOwl from UNMC:

ideffectiveTimeactivemoduleIdsourceIddestinationIdrelationshipGrouptypeIdcharacteristicTypeIdmodifierId
389446341000004000 19000000000002070007996353510000040001173620050370132008900000000000225000900000000000451000
154043481000004000 1900000000000207000799635351000004000641950000704320005900000000000011000900000000000451000
113689121000004000 19000000000002070007996353510000040004434120090116680003900000000000011000900000000000451000
953865841000004000 19000000000002070007996353510000040003676510030704319004900000000000011000900000000000451000
978593911000004000 19000000000002070007996353510000040004416520080704327008900000000000011000900000000000451000
326682591000004000 190000000000020700079963535100000400077604299100000400009216841000004100900000000000011000900000000000451000
557253841000004000 19000000000002070007996353510000040001185360000704318007900000000000011000900000000000451000
326573721000004000 19000000000002070007996353510000040001230290070370134009900000000000011000900000000000451000
232992231000004000 19000000000002070007996353510000040002580660000246501002900000000000011000900000000000451000

As can be seen, all relationship groups (role groups) are 0. Most attributes use to define observables are exclusive to the observables model, with