Issues for Mailing list of the Identity Cross-Reference Service and Retrieve, Locate and Update Service RTF

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 15895: EISMetaDataInterface.wsdl
Issue 15896: swpEISAdminEditorInterface.wsdl
Issue 16300: Error in specification document and in machine-consumable files
Issue 17121: The content of the specification doc is the IXS specification and not RLUS
Issue 17122: machine-consumable files are the same as in beta 2 version
Issue 17123: more serious inconsistences in machine-consumable files
Issue 17124: RLUSExpression.xsd is declared, in RLUSType.xsd, with the old intel namespace
Issue 17125: Reintroduce generic wsdl
Issue 17126: There are misalignments among specification document and the wsdls

Issue 15895: EISMetaDataInterface.wsdl (ixs-rlus-rtf)

EISMetaDataInterface.wsdl opens in Visual Web Developer 2008 with 90 warnings and 26 messages.  The well-formedness of this WSDL file needs to be investigated and corrections applied as necessary.
 

swpEISAdminEditorInterface.wsdl needs to be refactored to account for the update of the specification name to IXS.

 

1. The content of the specification doc is the IXS specification and not RLUS. Nothing of the RLUS spec (beta1 and 2) is in the document except some titles.


Solution: make use of beta 2 specification doc (if a new document does not exist)


2. The machine-consumable files are the same as in beta 2 version. In this version there are some serious inconsistences:


- The wsdl element "RLUSXMLSearch" does not exist in RLUSTypes.xsd. The correct element should be "RLUSSearchStruct" (or the RLUSTypes.xsd file uploaded is wrong). The issue affects get() list() and locate() operations.


- The RLUSTypes is declared as xmlns:RLUStypes="urn:RLUStypes.hssp.intel.com" and xmlns:xsd="http://www.omg.org/spec/RLUS/201012/RLUStypes" consequently some inconsistences arises in wsdls


- RLUSExpression.xsd is declared, in RLUSType.xsd, with the old intel namespace


Solution: correct wsdls


3. The "generic" wsdl (present in beta1) is missed. The generic wsdl should be the normative file. The specialized wsdls (order and patient) should be only examples


Solution: Reintroduce generic wsdl


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.

Error in specification document and in machine-consumable files

Issue 16300 is really multiple issues.  Each element is being submitted individually.

 

1. The content of the specification doc is the IXS specification and not RLUS. Nothing of the RLUS spec (beta1 and 2) is in the document except some titles.

 

 

Solution: make use of beta 2 specification doc (if a new document does not exist)

 

Issue 16300 is really multiple issues.  Each element is being submitted individually.

 

2. The machine-consumable files are the same as in beta 2 version. In this version there are some serious inconsistences:

 

 

- The wsdl element "RLUSXMLSearch" does not exist in RLUSTypes.xsd. The correct element should be "RLUSSearchStruct" (or the RLUSTypes.xsd file uploaded is wrong). The issue affects get() list() and locate() operations.

 

Issue 16300 is really multiple issues.  Each element is being submitted individually.  #2 is parsed into three issues:

 

2. The machine-consumable files are the same as in beta 2 version. In this version there are some serious inconsistences:

 

- The RLUSTypes is declared as xmlns:RLUStypes="urn:RLUStypes.hssp.intel.com" and xmlns:xsd="http://www.omg.org/spec/RLUS/201012/RLUStypes" consequently some inconsistences arises in wsdls
 

 

Issue 16300 is really multiple issues.  Each element is being submitted individually.  #2 is parsed into three issues:

 

2. The machine-consumable files are the same as in beta 2 version. In this version there are some serious inconsistences:

 

- RLUSExpression.xsd is declared, in RLUSType.xsd, with the old intel namespace

Issue 16300 is really multiple issues.  Each element is being submitted individually.

 

3. The "generic" wsdl (present in beta1) is missed. The generic wsdl should be the normative file. The specialized wsdls (order and patient) should be only examples

 

 

Solution: Reintroduce generic wsdl

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.