This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Constraints on infrastructureRoot attributes"

From HL7Wiki
Jump to navigation Jump to search
Line 27: Line 27:
 
*What are the use-cases for constraining InfrastructureRoot elements these?
 
*What are the use-cases for constraining InfrastructureRoot elements these?
 
*Belief that additional constraints on null flavors at the RIM attribute or datatype level may make sense (e.g PINF, NINF)
 
*Belief that additional constraints on null flavors at the RIM attribute or datatype level may make sense (e.g PINF, NINF)
 +
 +
Note that it's wrong to constrain templateId in any sense - it has no meaning,
 +
it is only provided to support instance validation, and no meaning may be
 +
associated with it. (From [[Clarification of use of templateid]])

Revision as of 00:39, 15 September 2006

Issue

There are four attributes listed in InfrastructureRoot: nullFlavor, realmCode, typeId and TemplateId.

Their use follows rules outside the mandates of the committees when performing their design work. A very conscious decision was made to not allow these attributes to be constrained by committees because it was felt that they should not be constrained (at least not in the usual manner - you can constrain nullFlavor with the mandatory indicator, and in MIF 2.0 you can require conformance with certain templates).

If things are supported by tooling or by the MIF, then that does not mean anything in terms of methodology. One can't conclude anything from something being supported by the MIF. Methodology leads, tools follow. Rene spronk 23:13, 21 Jun 2006 (CDT)

Discussion

However some people think this decision needs to be revisited (i.e. committees should be able to constrain these attributes when designing models).

Which is fine, and as usual puts the burden on those that don't agree with the current status quo to bring forward use-cases which may lead to the methodology being changed. I haven't seen that use-case yet. Rene spronk 23:13, 21 Jun 2006 (CDT)

The aim is to answer these questions, for each of them:

  1. Why it is there? ( document rules/decision )
  2. Could it be constrained in the cloned classes ( Is it allowed?)
  3. Should it be constrained in the cloned classes, if allowed ( should it be?)
  4. How it should be contrained in the cloned classed, if allowed (How do we do it?)

MnM Conference call 20060630

  • Question here should such constraints be applied? (RIM, D-MIMs, Templates?)
  • What are the use-cases for constraining InfrastructureRoot elements these?
  • Belief that additional constraints on null flavors at the RIM attribute or datatype level may make sense (e.g PINF, NINF)

Note that it's wrong to constrain templateId in any sense - it has no meaning, it is only provided to support instance validation, and no meaning may be associated with it. (From Clarification of use of templateid)