This wiki has undergone a migration to Confluence found Here
Difference between revisions of "March 6th, Agenda"
Jump to navigation
Jump to search
Line 11: | Line 11: | ||
### CC - Authoring APIs are a big difference. Is it important to standardise the update of vocabulary content? | ### 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. | ### 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 - 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. | + | ### 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. | + | ### RH - Could make sense if suggesting updates to the source. |
+ | ### SN - | ||
### Conformance Profiles | ### Conformance Profiles |
Latest revision as of 21:50, 6 March 2006
- 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 -
- Review of section 4.4 Functional Specification Conformance
- Conformance Profiles
- CTS 2 Conformance Profiles
- EHR Information Infrastructure
- Next Call
http://informatics.mayo.edu/wiki/index.php/March_6th%2C_Minutes