This wiki has undergone a migration to Confluence found Here
Difference between revisions of "SDWG/PHER-PHCR IG R2 Tularemia"
Jump to navigation
Jump to search
(→Issue) |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
{|width=100% cellspacing=0 cellpadding=2 border=1 | {|width=100% cellspacing=0 cellpadding=2 border=1 | ||
|| '''Submitted by:''' Sondra Renly | || '''Submitted by:''' Sondra Renly | ||
| − | || '''Revision date:''' | + | || '''Revision date:''' June 28, 2012 |
|- | |- | ||
|| '''Submitted date:''' May 15, 2012 | || '''Submitted date:''' May 15, 2012 | ||
| Line 20: | Line 20: | ||
# Figure 49 Location of Lesion Observation (p 110) uses SNOMED code 49755003 (lesion) which is not in the Tularemia value set. | # Figure 49 Location of Lesion Observation (p 110) uses SNOMED code 49755003 (lesion) which is not in the Tularemia value set. | ||
# Tularemia Result Organizer and Tularemia Result Observation constrain to the ValueSet 2.16.840.1.114222.4.11.3208 Lab Test Result Name (Tularemia). This list is out of date. | # Tularemia Result Organizer and Tularemia Result Observation constrain to the ValueSet 2.16.840.1.114222.4.11.3208 Lab Test Result Name (Tularemia). This list is out of date. | ||
| + | # Documentation refers to pending SNOMED request for term "Exposure to Francisella tularensis" with a temporary PHIN VADS code. Confirmed that no request had been submitted. Request submitted 06/21/2012 ID 58987. Jim Case approved term in US extension for release this August. | ||
== Recommendation == | == Recommendation == | ||
| − | + | # Change the Location of Lesion Observation code constraint to ValueSet 2.16.840.1.114222.4.11.3215 Signs and Symptoms (Tularemia). | |
| + | # Review ValueSet 2.16.840.1.114222.4.11.3215 Signs and Symptoms (Tularemia) to determine if Lesion (49755003) should be in the value set (change request to PHIN VADS) or if the example should be changed to use an existing code from the value set. | ||
| + | # PHIN VADS has a current ValueSet 2.16.840.1.114222.4.11.4217 Lab Test Name (Tularemia). Review and discuss with VADS team about ownership and ongoing maintenance needs to determine if the current or newer ValueSet should be referenced going forward. | ||
| + | # Update documentation with SNOMED code after August. | ||
== Rationale == | == Rationale == | ||
Latest revision as of 20:55, 28 June 2012
Return to PHER page; Return to Change Requests for PHER Standards page.
| Submitted by: Sondra Renly | Revision date: June 28, 2012 |
| Submitted date: May 15, 2012 | Change request ID: <<Change Request ID>> |
| Standard: SDWG/PHER-PHCR IG R2 | Artifact ID, Name: <<Artifact ID, Name>> |
Issue
- The Tularemia Case Report Location of Lesion Observation [observation: templateId 2.16.840.1.113883.10.20.15.3.44] documented on page 109 is part of the Tularemia Case Observation (p79). This template constraints the value/@code to an Acute Hep B value set.
- Figure 49 Location of Lesion Observation (p 110) uses SNOMED code 49755003 (lesion) which is not in the Tularemia value set.
- Tularemia Result Organizer and Tularemia Result Observation constrain to the ValueSet 2.16.840.1.114222.4.11.3208 Lab Test Result Name (Tularemia). This list is out of date.
- Documentation refers to pending SNOMED request for term "Exposure to Francisella tularensis" with a temporary PHIN VADS code. Confirmed that no request had been submitted. Request submitted 06/21/2012 ID 58987. Jim Case approved term in US extension for release this August.
Recommendation
- Change the Location of Lesion Observation code constraint to ValueSet 2.16.840.1.114222.4.11.3215 Signs and Symptoms (Tularemia).
- Review ValueSet 2.16.840.1.114222.4.11.3215 Signs and Symptoms (Tularemia) to determine if Lesion (49755003) should be in the value set (change request to PHIN VADS) or if the example should be changed to use an existing code from the value set.
- PHIN VADS has a current ValueSet 2.16.840.1.114222.4.11.4217 Lab Test Name (Tularemia). Review and discuss with VADS team about ownership and ongoing maintenance needs to determine if the current or newer ValueSet should be referenced going forward.
- Update documentation with SNOMED code after August.
Rationale
Discussion
Recommended Action Items
Resolution
(Resolution is to be recorded here and in the referenced minutes, which are the authoritative source of resolution).
