Stream: implementers
Topic: Aggregate vs distinct profiles
Sadiq Saleh (Jan 26 2017 at 19:51):
Hi,
I was looking for some insight as to cases when one would put together an profile package (such as vital signs, QICore, or DAF) compared to distinct profiles? Does the existing tooling support building such packages?
From what I understand, in the case of the vital signs profile, this is when then a profile (e.g. BMI) must conform to two sets of profiles:
1) the parent profile - it. must conform to all the criteria of the vital signs profile
2) a specific profile - it must also conform to additional constraints as part of the BMI profile specifically
Does this differ from just building these profiles independently but still authoring it such that the profile has both sets of constraints?
Thanks in advance.
Lloyd McKenzie (Jan 27 2017 at 23:02):
The main reason for deriving one profile from another is to simplify maintenance. If you update the parent profile, those changes will automatically ripple down into the chlidren. (Note that profile dependency is independent from profile packaging - packaging is purely a question of how you want to publish things.
Last updated: Apr 12 2022 at 19:14 UTC
