This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
Definition for Code System OrderSetItemGroupingBehavior
<CodeSystem xmlns="http://hl7.org/fhir"> <id value="grouping-behavior"/> <meta> <lastUpdated value="2016-03-31T08:01:25.570+11:00"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2>OrderSetItemGroupingBehavior</h2> <p>Defines organization behavior of a group</p> <p>This code system http://hl7.org/fhir/grouping-behavior defines the following codes:</p> <table class="codes"> <tr> <td> <b>Code</b> </td> <td> <b>Display</b> </td> <td> <b>Definition</b> </td> </tr> <tr> <td>visual-group <a name="visual-group"> </a> </td> <td>Visual Group</td> <td>Any group marked with this behavior should be displayed as a visual group to the end user</td> </tr> <tr> <td>logical-group <a name="logical-group"> </a> </td> <td>Logical Group</td> <td>A group with this behavior logically groups its sub-elements, and may be shown as a visual group to the end user, but it is not required to do so</td> </tr> <tr> <td>sentence-group <a name="sentence-group"> </a> </td> <td>Sentence Group</td> <td>A group of related alternative items is a sentence group if the target referenced by the item is the same in all the items, and each item simply constitutes a different variation on how to specify the details for the target. For example, two items that could be in a SentenceGroup are "aspirin, 500 mg, 2 times per day" and "aspirin, 300 mg, 3 times per day". In both cases, aspirin is the target referenced by the item, and the two items represent two different options for how aspirin might be ordered for the patient. Note that a SentenceGroup would almost always have an associated selection behavior of "AtMostOne", unless it's a required item, in which case, it would be "ExactlyOne"</td> </tr> </table> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid"> <valueUri value="urn:oid:2.16.840.1.113883.4.642.1.503"/> </extension> <url value="http://hl7.org/fhir/grouping-behavior"/> <version value="1.4.0"/> <name value="OrderSetItemGroupingBehavior"/> <status value="draft"/> <experimental value="false"/> <publisher value="HL7 (FHIR Project)"/> <contact> <telecom> <system value="other"/> <value value="http://hl7.org/fhir"/> </telecom> <telecom> <system value="email"/> <value value="fhir@lists.hl7.org"/> </telecom> </contact> <date value="2016-03-31T08:01:25+11:00"/> <description value="Defines organization behavior of a group"/> <caseSensitive value="true"/> <valueSet value="http://hl7.org/fhir/ValueSet/grouping-behavior"/> <content value="complete"/> <concept> <code value="visual-group"/> <display value="Visual Group"/> <definition value="Any group marked with this behavior should be displayed as a visual group to the end user"/> </concept> <concept> <code value="logical-group"/> <display value="Logical Group"/> <definition value="A group with this behavior logically groups its sub-elements, and may be shown as a visual group to the end user, but it is not required to do so"/> </concept> <concept> <code value="sentence-group"/> <display value="Sentence Group"/> <definition value="A group of related alternative items is a sentence group if the target referenced by the item is the same in all the items, and each item simply constitutes a different variation on how to specify the details for the target. For example, two items that could be in a SentenceGroup are "aspirin, 500 mg, 2 times per day" and "aspirin, 300 mg, 3 times per day". In both cases, aspirin is the target referenced by the item, and the two items represent two different options for how aspirin might be ordered for the patient. Note that a SentenceGroup would almost always have an associated selection behavior of "AtMostOne", unless it's a required item, in which case, it would be "ExactlyOne""/> </concept> </CodeSystem>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.