This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "CTS2N - 02-Jul-13"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "Minutes 02-Jul-2013= == Roll Call == === Present === * Frank Oemig * Ana Estelrich * Carmela Couderc * Senthil Nachimuthu * Russ Hamm == Agenda Check == * No changes == ...")
 
 
Line 25: Line 25:
 
Proposed reconciliation for these items is as follows.  Items are found to be persuasive.  Disposition is to remove notification functionality from sections 2 and 5, and include an updated diagram (example below) indicating that CTS 2 has an optional dependency on a notification service.  Also include references published by the OMG such as the Notification (NOT) service framework and the OMG Data-Distribution Service Framework (DDS) as example notification services.  Lastly, indicate in the Changes from Previous version section (preface) that notification functionality has been removed.
 
Proposed reconciliation for these items is as follows.  Items are found to be persuasive.  Disposition is to remove notification functionality from sections 2 and 5, and include an updated diagram (example below) indicating that CTS 2 has an optional dependency on a notification service.  Also include references published by the OMG such as the Notification (NOT) service framework and the OMG Data-Distribution Service Framework (DDS) as example notification services.  Lastly, indicate in the Changes from Previous version section (preface) that notification functionality has been removed.
  
Proposed wording for the diagram below:  “At a minimum, it is expected that CTS 2 will make use of an Entity Identification Service, and Notification service which in turn will reference a set of Security Services. CTS 2 itself will make use of the Security Services to implement its own functional profile restrictions. Services such as a Decision Support Service, Clinical Research Functional Query, and Resource Locate and Update Service may find the use of the CTS 2 service a key resource in improving content disambiguation.”
+
Proposed wording for the diagram called HSSP Service Architecture present in the 2009 draft:  “At a minimum, it is expected that CTS 2 will make use of an Entity Identification Service, and Notification service which in turn will reference a set of Security Services. CTS 2 itself will make use of the Security Services to implement its own functional profile restrictions. Services such as a Decision Support Service, Clinical Research Functional Query, and Resource Locate and Update Service may find the use of the CTS 2 service a key resource in improving content disambiguation.”
 +
 
 +
Reconciliation on ballot item 47,48,50,521,52,6,15,34 (A-T)
 +
Propose block vote on the above ballot items dealing with miscellaneous spelling corrections
 +
Proposed reconciliation for these items is as follows.  Items are found to be persuasive; all spelling suggestions will be accepted.

Latest revision as of 14:47, 10 September 2013

Minutes 02-Jul-2013=

Roll Call

Present

  • Frank Oemig
  • Ana Estelrich
  • Carmela Couderc
  • Senthil Nachimuthu
  • Russ Hamm

Agenda Check

  • No changes

Announcements

No announcements.

Voting Decision Making Practices Review

For the time being CTS2 will bring our suggested dispositions to the Vocab WG for formal vote. CTS 2 Ballot reconciliation has been added to the main Vocab WG calls.

Ballot Reconciliation

Reconciliation on ballot item 14,16,19,20,21,25,26,27 dealing with notification functionality being out of scope for CTS2. Propose block vote on the above ballot items dealing with notification functionality. Proposed reconciliation for these items is as follows. Items are found to be persuasive. Disposition is to remove notification functionality from sections 2 and 5, and include an updated diagram (example below) indicating that CTS 2 has an optional dependency on a notification service. Also include references published by the OMG such as the Notification (NOT) service framework and the OMG Data-Distribution Service Framework (DDS) as example notification services. Lastly, indicate in the Changes from Previous version section (preface) that notification functionality has been removed.

Proposed wording for the diagram called HSSP Service Architecture present in the 2009 draft: “At a minimum, it is expected that CTS 2 will make use of an Entity Identification Service, and Notification service which in turn will reference a set of Security Services. CTS 2 itself will make use of the Security Services to implement its own functional profile restrictions. Services such as a Decision Support Service, Clinical Research Functional Query, and Resource Locate and Update Service may find the use of the CTS 2 service a key resource in improving content disambiguation.”

Reconciliation on ballot item 47,48,50,521,52,6,15,34 (A-T) Propose block vote on the above ballot items dealing with miscellaneous spelling corrections Proposed reconciliation for these items is as follows. Items are found to be persuasive; all spelling suggestions will be accepted.