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

Difference between revisions of "April 14th 2009 CBCC Conference Call"

From HL7Wiki
Jump to navigation Jump to search
Line 18: Line 18:
 
# ''(45 min)'' '''Balloting Composite Privacy Consent as a normative or DSTU standard'''  
 
# ''(45 min)'' '''Balloting Composite Privacy Consent as a normative or DSTU standard'''  
 
#* 1. Develop a V3 messaging specification (PubDB, R-MIM designer) - R-MIM Designer is slated for obsolescence. A lot of work would be required, resulting specification is not very accessible to new implementers in the US. However the revisions made in this version may be useful in Canada. Would Canada be interested in publishing the V3 message topic?
 
#* 1. Develop a V3 messaging specification (PubDB, R-MIM designer) - R-MIM Designer is slated for obsolescence. A lot of work would be required, resulting specification is not very accessible to new implementers in the US. However the revisions made in this version may be useful in Canada. Would Canada be interested in publishing the V3 message topic?
#* 2. Propose that Composite Privacy Consent Directive (CPCD) become a pilot SAEAF project - demonstrating how we design service-aware standards. Pending approval from the Enterprise Application Implementation Planning (EA IP) project. Contact Marc Koehn - project lead for EAIP - and propose our standard. EAIP is looking for candidate service-aware pilot projects. Since the SAEAF is not completed, there is some uncertainty regarding the timeline. How does a project sign up to be a SAEAF pilot, what are the criteria? If a project is approved as a SAEAF pilot, what the is earliest we could publish our specification as a DSTU?
+
#* 2. Propose that Composite Privacy Consent Directive (CPCD) become a pilot SAEAF project - demonstrating how we design service-aware standards. Pending approval from the Enterprise Application Implementation Planning [[EA IP]] project. Contact Marc Koehn - project lead for EAIP - and propose our standard. EAIP is looking for candidate service-aware pilot projects. Since the SAEAF is not completed, there is some uncertainty regarding the timeline. How does a project sign up to be a SAEAF pilot, what are the criteria? If a project is approved as a SAEAF pilot, what the is earliest we could publish our specification as a DSTU?
 
#* 3. Work with SOA WG and add to the existing PASS Audit and PASS Access Control two new service functional specifications: PASS Privacy Policy Mgmt/Lookup, PASS Consent Directive Mgmt/Lookup. In addition to the service functional specifications we could also issue an OMG RFC (request for comment) for our technical service specification (including XSDs, etc.). Ask Gila Pyke, Ken Rubin, and Galen Mulrooney how we could ballot a service functional spec in HL7 in July and in OMG.
 
#* 3. Work with SOA WG and add to the existing PASS Audit and PASS Access Control two new service functional specifications: PASS Privacy Policy Mgmt/Lookup, PASS Consent Directive Mgmt/Lookup. In addition to the service functional specifications we could also issue an OMG RFC (request for comment) for our technical service specification (including XSDs, etc.). Ask Gila Pyke, Ken Rubin, and Galen Mulrooney how we could ballot a service functional spec in HL7 in July and in OMG.
  

Revision as of 23:03, 20 April 2009

Community-Based Collaborative Care Working Group Meeting


Attendees

  1. Ioana Singureanu Scribe
  2. Suzanne Gonzales-Webb - CBCC Co-chair
  3. Richard Thoreson
  4. Tony Weida
  5. Rich Furr
  6. Milan Petkovic

Agenda

  1. (5 min) Roll Call
  2. (10 min) Harmonization - 4th quarter, 6:30-8:00 EDT, Conference line: 770-657-9270:459876
  3. (45 min) Balloting Composite Privacy Consent as a normative or DSTU standard
    • 1. Develop a V3 messaging specification (PubDB, R-MIM designer) - R-MIM Designer is slated for obsolescence. A lot of work would be required, resulting specification is not very accessible to new implementers in the US. However the revisions made in this version may be useful in Canada. Would Canada be interested in publishing the V3 message topic?
    • 2. Propose that Composite Privacy Consent Directive (CPCD) become a pilot SAEAF project - demonstrating how we design service-aware standards. Pending approval from the Enterprise Application Implementation Planning EA IP project. Contact Marc Koehn - project lead for EAIP - and propose our standard. EAIP is looking for candidate service-aware pilot projects. Since the SAEAF is not completed, there is some uncertainty regarding the timeline. How does a project sign up to be a SAEAF pilot, what are the criteria? If a project is approved as a SAEAF pilot, what the is earliest we could publish our specification as a DSTU?
    • 3. Work with SOA WG and add to the existing PASS Audit and PASS Access Control two new service functional specifications: PASS Privacy Policy Mgmt/Lookup, PASS Consent Directive Mgmt/Lookup. In addition to the service functional specifications we could also issue an OMG RFC (request for comment) for our technical service specification (including XSDs, etc.). Ask Gila Pyke, Ken Rubin, and Galen Mulrooney how we could ballot a service functional spec in HL7 in July and in OMG.




Back to Meetings