-
Key: CTS2F2-34
-
Legacy Issue Number: 17115
-
Status: closed
-
Source: Mayo Clinic ( Mr. Craig Stancl)
-
Summary:
Derivation and derivationReasoningAlgorithm shouldn't be marked as
{readOnly}, as it is not part of the identity of Association. These two fields need to be added as optparams in UpdateAssociationRequest (Needs to be changed in the WADL and Schema as well.
Logged: https://github.com/cts2/cts2-specification/issues/37
-
Reported: CTS2 1.0b1 — Thu, 9 Feb 2012 05:00 GMT
-
Disposition: Resolved — CTS2 1.0
-
Disposition Summary:
PIM:
Updated Diagram (Figure 4.1: Association Model. Association, Page 43.)
Updated Diagram (Figure 5.4: Association Maintenance. Association, Page 67.)PSM:
Add the following elements to the 'UpdateAssociationRequest' type:
<xs:element minOccurs="0" name="updatedDerivation">
<xs:complexType>
<xs:sequence>
<xs:element name="derivation" type="association:AssociationDerivation" minOccurs="1" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
</xs:element>
and
<xs:element minOccurs="0" name="updatedDerivationReasoningAlgorithm">
<xs:complexType>
<xs:sequence>
<xs:element name="derivationReasoningAlgorithm" type="core:ReasoningAlgorithmReference" minOccurs="1" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
</xs:element> -
Updated: Fri, 6 Mar 2015 20:58 GMT
CTS2F2 — Association Information Model derivation and derivationReasoningAlgorithm
- Key: CTS2F2-34
- OMG Task Force: Common Terminology Services 2 (CTS2) FTF