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

Difference between revisions of "March 6th, Agenda"

From HL7Wiki
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
# Roll Call
 +
## Russell Hamm (RH)
 +
## Joann Larson (JL)
 +
## Chengjian Che (CC)
 +
## Senthil Nachimuthu (SN)
 +
 +
# Agenda Check
 +
## Review of section 4.4 Functional Specification Conformance
 +
### Overview of 4.4 Table.
 +
### JL - Looks good.  May need formal conformance mapping at some point.
 +
### CC - Authoring APIs are a big difference.  Is it important to standardise the update of vocabulary content? 
 +
### JL - This comes up in serveral domains (in EHR, and in HITSP.)  Specifically, how to manage versioning.
 +
### CC - SNOMED makes a change to version from '05 to '06.  This is version management.
 +
### CC - From Russ' use case it makes sense to standardise the functions, since we are changing a local copy of a vocabulary, and not the source. 
 +
### RH - Could make sense if suggesting updates to the source.
 +
### SN -
 +
 +
### Conformance Profiles
 +
### CTS 2 Conformance Profiles
 +
## EHR Information Infrastructure
 +
# Next Call
 +
 
http://informatics.mayo.edu/wiki/index.php/March_6th%2C_Minutes
 
http://informatics.mayo.edu/wiki/index.php/March_6th%2C_Minutes

Latest revision as of 21:50, 6 March 2006

  1. Roll Call
    1. Russell Hamm (RH)
    2. Joann Larson (JL)
    3. Chengjian Che (CC)
    4. Senthil Nachimuthu (SN)
  1. Agenda Check
    1. Review of section 4.4 Functional Specification Conformance
      1. Overview of 4.4 Table.
      2. JL - Looks good. May need formal conformance mapping at some point.
      3. CC - Authoring APIs are a big difference. Is it important to standardise the update of vocabulary content?
      4. JL - This comes up in serveral domains (in EHR, and in HITSP.) Specifically, how to manage versioning.
      5. CC - SNOMED makes a change to version from '05 to '06. This is version management.
      6. CC - From Russ' use case it makes sense to standardise the functions, since we are changing a local copy of a vocabulary, and not the source.
      7. RH - Could make sense if suggesting updates to the source.
      8. SN -
      1. Conformance Profiles
      2. CTS 2 Conformance Profiles
    1. EHR Information Infrastructure
  1. Next Call

http://informatics.mayo.edu/wiki/index.php/March_6th%2C_Minutes