Templates DSTU 1 Comments

Related Links Templates Home Page

Templates DSTU Release 1 Comments

Back to Templates WG langing page

Invitation to submit DSTU 1 comments

Invitation to submit DSTU 1 comments

During the time the HL7 Templates Standard: Specification and Use of Reusable Information Constraint Templates, Release 1 is a DSTU you are invited to submit your comments here.

Please submit a new section at the end of this page and do not forget to sign it by adding your name and date, preferably by adding the macro ~~~~ at the end of your edit.

Add a new comment section

Templates life-cycle state terms

The Trifolia team would like to submit a DSTU Comment against the Templates DSTU ...

Here’s the issue:

We have found inconsistency in two of the “life-cycle” state terms. The Templates DSTU used the terms "Retired" and "Terminated" in a way that is inconsistent with the way the HL7 Harmonization Process uses these words. Also, HL7 Harmonization uses "Deprecated" and "Retired". Trifolia uses the terms "Deprecated" and “Retired”. However, we don’t think that everyone is using the term “Retired” to mean the same thing. Also, the ActStatus code system needs to be reviewed to see where these "states" are actually defined within HL7.

All this needs to get further clarified, and then the DSTU should be updated to reflect the agreed “common” view/usage.

Sarah will confirm the definitions as they are being used in Trifolia.

If you add this topic to a discussion item at a Templates Meeting and let this group know when that discussion could take place, we will send representatives to help work through this. We think Vocab (due to Harmonization Process overlap) and M&M should also be included in the analysis/discussion. The material in question can be found in chapter 2.9.6 in the Templates DSTU.

Lisa Nelson (talk) 07:47, 21 October 2014 (UTC)

The state terms are drawn from the Document HL7 Templates Business Process Requirements Analysis, previously balloted successfully by the Templates WG in 2012. In Chapter 6.3 TEMPLATE METADATA INFORMATION LIFECYCLE MANAGEMENT you'll find the state terms and their descriptions. Kai (talk) 08:00, 21 October 2014 (UTC)

Cardinality constraint

Original Ballot Reconciliation Item#70 Templates Sec 2.10.3

Original text: choice to be one out of n (cardinality constraint).

• Ballot comment Frank Oemig 2014-05

this is not a cardinality constraint. It would be good to see an example where n out of m choice elements are selected! This is just for choices if I have to repeat an element n times and to present n different selections.

• Templates Work Group comment 2014-09-19

Why not? It says something about the mulitplicity of the choice set members. What would be the correct term? Will add more examples.

• Frank's comment 2014-10-15

Constraining choices has two aspects: a) constraining the selectable branches and b) the cardinality.

You start with b) and uses an exmple for a).

Optional conformance

Original Ballot Reconciliation Item#103 Templates sec 7.4.1.5

Original text: O - optional

• Ballot comment Frank Oemig 2014-05

what about optional?

• Templates Work Group comment 2014-09-19

In this specification "optional" is derived (minimumMultiplicity = 0 and no other conformance specified). Do you think one need to be able to explicitly specify this redundantly?

• Frank's comment 2014-10-15

it is not the same: "R"is SHOULD while "O" is "MAY". So: yes.

Better example for choices

Original Ballot Reconciliation Item#108 Templates sec 7.4.12

• Ballot comment Frank Oemig 2014-05

we should have an example here…

• Templates Work Group comment 2014-09-19

There is one example for choice! What else do you wish to see?

• Frank's comment 2014-10-15

it refers to my other comment about choices. A better example would be to use the clinical statement pattern. You may constrain the number to say it must contain 2..* items (cardinality) out of reduced set (observation, procedure, substanceAdmin).

Constraints

Original Ballot Reconciliation Item#109 Templates sec 7.4.13

Original text: .. Transparent to the user

• Ballot comment Frank Oemig 2014-05

It must be visible whether a constraint is inherited or new!

• Templates Work Group comment 2014-09-19

What do you mean by this choice ""inherited"" or ""new""? You simple include the constraints specified in the mentioned template, that theoretically can be in any status. This is about inclusion and we will add another example on how inclusion actually works plus a statement that cardinalities in include statements overrides the cards of the root element(s) of the included template. We will also add that the change of cardinalities may not violate any formal restrictive conformance rules."

• Frank's comment 2014-10-15

it sohuld be made visible whether within this specification an attribute has more constraints than in the underlying one.

Example of Trifolia

Original Ballot Reconciliation Item#112 Templates sec 7.5.3

• Ballot comment Frank Oemig 2014-05

where is an example of Trifolia?

• Templates Work Group comment 2014-09-19

The examples later are the MS-Word output from Trifolia. We will add additional screenshots of Trifolia for your convenience

• Frank's comment 2014-10-15

Section 11.1 now reflects the experience CGIT has made with SDWG. They stopped their cooperation after discussiing our comments on their approach.