There are misalignments among specification document and the wsdls
Legacy Issue Number: 17126
Source: Sparx Systems Pty Ltd ( J.D. Baker)
Issue 16300 is really multiple issues. Each element is being submitted individually.
4. There are misalignments among specification document and the wsdls:
- The specification document (obviously I'm referring to beta 1/2 version) consider only the operation specified in beta 1 wsdls. However the beta2 wsdls includes new operations (findDuplicateDefinitions(), linkRecords(), unlinkRecords(), mergeRecords(), unMergeRecords(), inactivateRecord(), reactivateRecord(), cancelOrder(), detectDuplicateOrder() ). For the new operations there is some minor issue of naming style, it's not consistent with the originals operations from beta 1.
- Note: some new operations refer to a specific scenario (cancelOrder(), detectDuplicateOrder() ). However in RLUS is very relevant the separation of concerns between operations and Semantic Signifier. This aspect it’s relevant in RTF work. In general I think that the semantic aspects should be conveyed only in the Semantic Signifier and not in in other elements of the wsdl (this consideration is not an element of the urgent fix).
Solution: The normative "generic" wsdl must be consistent with the specification document. The new operations can be considered (and documented in wsdls) as “experimental” and included only in wsdls specific example (order, patient).
Some of the new interesting feature, possibly, will be included the new HL7 SFM in the meantime.
Reported: IXS 1.0b1 — Mon, 13 Feb 2012 05:00 GMT
Updated: Sat, 7 Mar 2015 03:43 GMT