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

Difference between revisions of "20110331 arb minutes"

From HL7Wiki
Jump to navigation Jump to search
Line 112: Line 112:
 
==Minutes==
 
==Minutes==
  
 
+
#Call to order Call to order at 4:07
#Call to order  
 
 
#Approval of Agenda  
 
#Approval of Agenda  
 
#approval of Minutes  
 
#approval of Minutes  
 
#HDATA dialog  
 
#HDATA dialog  
##Jane presented a picture representing the relationships between WG's.
+
##Jane presented a picture representing the relationships between WG's.[[File:Janes-picture.png|400px|thumb|right|Janes-Diagram]]  
[[File:Janes-picture.png|400px|thumb|right|Janes-Diagram]]  
 
 
##The right side is how we look at it
 
##The right side is how we look at it
 
##The left side is how it SHOULD be done
 
##The left side is how it SHOULD be done
 
##Cecil: You need a business analyst to sit between the technical architects and the Domain experts.  This falls out in the Inplementation Guide.  There are inward and outward facing views for each of the roles.
 
##Cecil: You need a business analyst to sit between the technical architects and the Domain experts.  This falls out in the Inplementation Guide.  There are inward and outward facing views for each of the roles.
 +
##Ron: This is an excellent model that is valuable for elaboration from the canonical SAIF to the Implementation Guide.
 +
##Jane: I thought that HDATA has two elements - transformation from generalized design into specific one, where business names are substituted for generic structure names - a manual and intensive mental excercise. 
 +
##Gerald: right - the hdata names are different than the model names.  There could be direct correspondence to HL7 templates to create an HDATA content profile.
 +
##Paul Knapp: Listening to the discussion you are agreeing in words, but not in fact.  I dont see any ITS in HDATA.  You are not taking the semantic model and templating structure, and rendering in some other ITS that is HDATA specific.  HDATA is a packaging of an already rendered good.
 +
##Paul Knapp: A CDA is a good that gets packaged.
 +
##Jane Curry: It does not get packaged until it is mapped.
 +
##Paul Knapp: After it is packaged.
 +
##Gerald: Reliant on the mapping.  May be a collection of goods with relationships, then would have structure.
 +
##Paul Knapp: If I get a box to hold goods, the structure of the box does not speak to the assembly of the structures in the box.
 +
##Gerald: HDATA includes a description of how to package the items in the box.
 +
##Paul Knapp: Currently the semantic model is ran through ITS to create  Good.  HDATA does not render the data into a good.  A good anology is a ZIP file.  Zip does not interface with the methodology of the content provider.
 +
##Gerald: The content profiles define how the zip file is organized.
 +
##Briah: It is a manifest.
 +
##Paul Knapp:It is a rich manifest.  I am trying to get HDATA positioned in the process - it is a step AFTER the ITS has been applied.  It belongs below the ITS box.
 +
##Jane: It is an HL7 recognized packaging mechanism.
 +
##Gerald: Package and service.  We have talked to John Koisch on how it maps to RLUS.
 +
##Ron Parker: Helps shape thinking on how ITS are utilized.
 +
##Cecil Lynch: I can see applying the hdata zip to the ITS, but I cant see how to take the elements created in HDATAZ, and unpackage unto a compliant HL7construct.
 +
##Paul Knapp: You can take a CDA and put it in a zip, and extract it.  Same with HDATA.
 +
##Cecil: I cant see that from the schema's.
 +
##Gerald: Dont get hung up on the schema's.  We are starting to understand that we ar susing HL7 v3 artifacts, or message set, and transporting in its entirety.
  
 
#SAIF program progress.  
 
#SAIF program progress.  
Line 128: Line 147:
 
#Other business and planning for next meeting  
 
#Other business and planning for next meeting  
 
#Adjournment  
 
#Adjournment  
 
 
  
 
[[Category:Arb Minutes]]
 
[[Category:Arb Minutes]]
 
   [[User:Ajulian|Tony Julian]] 17:33, 31 January 2011 (UTC)
 
   [[User:Ajulian|Tony Julian]] 17:33, 31 January 2011 (UTC)

Revision as of 20:37, 31 March 2011

ArB Agenda/Minutes

logistics

Time: 4:00pm U.S. Eastern


Please consult http://www.timeanddate.com/worldclock for your local times

1. Please join my meeting. https://www2.gotomeeting.com/join/535702651


Or go to www.gotomeeting.com At the top of the page click on the join meeting button

Then enter Meeting ID: Meeting ID: 535-702-651


2. Join the conference call: Dial 770-657-9270 Passcode 854126#

Agenda

  1. Call to order
  2. Approval of Agenda
  3. approval of Minutes
  4. HDATA dialog
  5. SAIF program progress.
  6. Glossary vs Index
  7. Implementation guide(s - aka where do we go from here?
  8. Other business and planning for next meeting
  9. Adjournment

Meeting Information

HL7 ArB Work Group Meeting Minutes

Location: Telcon

Date: 20110331
Time: 4:00pm U.S. Eastern
Facilitator Ron Parker Note taker(s) Tony Julian
Attendee Name Affiliation
. Bond,Andy NEHTA
. Curry, Jane Health Information Strategies
. Grieve, Grahame Kestral Computing
. Hufnagel, Steve U.S. Department of Defense, Military Health System
. Julian, Tony Mayo Clinic
. Koisch, John Guidewire Architecture
. Loyd, Patrick Gordon point Informatics LTD.
. Lynch, Cecil ontoreason LLC
. Mead, Charlie National Cancer Institute
. Ocasio, Wendell Agilex Technologies
. Parker, Ron CA Infoway
. Quinn, John Health Level Seven, Inc.
. Shakir, Abdul-Malik Shakir Consulting
. Guests
. Haddorff, Rick Mayo Clinic
. Laskso, Lynn HL7 Staff
. Milosevic, Zoran NEHTA
Quorum Requirements Met: Yes

Minutes

  1. Call to order Call to order at 4:07
  2. Approval of Agenda
  3. approval of Minutes
  4. HDATA dialog
    1. Jane presented a picture representing the relationships between WG's.
      Janes-Diagram
    2. The right side is how we look at it
    3. The left side is how it SHOULD be done
    4. Cecil: You need a business analyst to sit between the technical architects and the Domain experts. This falls out in the Inplementation Guide. There are inward and outward facing views for each of the roles.
    5. Ron: This is an excellent model that is valuable for elaboration from the canonical SAIF to the Implementation Guide.
    6. Jane: I thought that HDATA has two elements - transformation from generalized design into specific one, where business names are substituted for generic structure names - a manual and intensive mental excercise.
    7. Gerald: right - the hdata names are different than the model names. There could be direct correspondence to HL7 templates to create an HDATA content profile.
    8. Paul Knapp: Listening to the discussion you are agreeing in words, but not in fact. I dont see any ITS in HDATA. You are not taking the semantic model and templating structure, and rendering in some other ITS that is HDATA specific. HDATA is a packaging of an already rendered good.
    9. Paul Knapp: A CDA is a good that gets packaged.
    10. Jane Curry: It does not get packaged until it is mapped.
    11. Paul Knapp: After it is packaged.
    12. Gerald: Reliant on the mapping. May be a collection of goods with relationships, then would have structure.
    13. Paul Knapp: If I get a box to hold goods, the structure of the box does not speak to the assembly of the structures in the box.
    14. Gerald: HDATA includes a description of how to package the items in the box.
    15. Paul Knapp: Currently the semantic model is ran through ITS to create Good. HDATA does not render the data into a good. A good anology is a ZIP file. Zip does not interface with the methodology of the content provider.
    16. Gerald: The content profiles define how the zip file is organized.
    17. Briah: It is a manifest.
    18. Paul Knapp:It is a rich manifest. I am trying to get HDATA positioned in the process - it is a step AFTER the ITS has been applied. It belongs below the ITS box.
    19. Jane: It is an HL7 recognized packaging mechanism.
    20. Gerald: Package and service. We have talked to John Koisch on how it maps to RLUS.
    21. Ron Parker: Helps shape thinking on how ITS are utilized.
    22. Cecil Lynch: I can see applying the hdata zip to the ITS, but I cant see how to take the elements created in HDATAZ, and unpackage unto a compliant HL7construct.
    23. Paul Knapp: You can take a CDA and put it in a zip, and extract it. Same with HDATA.
    24. Cecil: I cant see that from the schema's.
    25. Gerald: Dont get hung up on the schema's. We are starting to understand that we ar susing HL7 v3 artifacts, or message set, and transporting in its entirety.
  1. SAIF program progress.
  2. Glossary vs Index
  3. Implementation guide(s - aka where do we go from here?
  4. Other business and planning for next meeting
  5. Adjournment
 Tony Julian 17:33, 31 January 2011 (UTC)