This wiki has undergone a migration to Confluence found Here
Difference between revisions of "SNOMED Submission Process Draft Outline"
Jump to navigation
Jump to search
| (6 intermediate revisions by 2 users not shown) | |||
| Line 8: | Line 8: | ||
== How is it Determined that a Given Request is Valid for Submission? == | == How is it Determined that a Given Request is Valid for Submission? == | ||
| + | * Is the content domain valid for SNOMED | ||
| + | * Is the request provided in such a way that the intent of the request can be ascertained? | ||
| + | * Is there a justification or rationale provided for the content request? | ||
| + | * Is the content request of the appropriate granularity? | ||
| + | * Is the requested content parent in the appropriate SNOMED hierarchy? | ||
| + | * Is the content requested in the appropriate location within the hierarchy? (i.e. does an appropriate parent concept exist?) | ||
| + | * Does the concept already exist in SNOMED? | ||
| + | * Is the requested content a synonym for an existing concept? | ||
| + | * Is the requested content change ambiguous? | ||
| + | * Are there at least two Realms that will support the proposed content change request? | ||
| + | |||
| + | == How are Request Submissions Packaged? == | ||
| − | + | * '''CONSIDERATION:''' "Related" content changes should be packaged together and submitted as a whole. | |
| − | * | + | * '''CONSIDERATION:''' Multiple unrelated content changes should be submitted separately |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| + | * '''CONSIDERATION:''' Should HL7 obtain its own SNOMED namespace? | ||
== Who within HL7 can Request a SNOMED Submission == | == Who within HL7 can Request a SNOMED Submission == | ||
| + | * | ||
== Who within HL7 can Submit a SNOMED Submission == | == Who within HL7 can Submit a SNOMED Submission == | ||
| + | * | ||
| + | == Who within HL7 is responsible for Managing SNOMED Submissions == | ||
* | * | ||
| Line 33: | Line 43: | ||
== What is the Communication Plan in HL7 wrt the Status of Requests == | == What is the Communication Plan in HL7 wrt the Status of Requests == | ||
| − | + | * If content change requests are rejected, how to communicate the information to the proponent to ensure it the change request is captured in the proponent's international extension? | |
== When == | == When == | ||
== Where == | == Where == | ||
Latest revision as of 15:08, 29 October 2010
Contents
- 1 How is it Determined When a Content Change for SNOMED- is Needed?
- 2 How is it Determined that a Given Request is Valid for Submission?
- 3 How are Request Submissions Packaged?
- 4 Who within HL7 can Request a SNOMED Submission
- 5 Who within HL7 can Submit a SNOMED Submission
- 6 Who within HL7 is responsible for Managing SNOMED Submissions
- 7 Who can Validate Domain Specific Requests?
- 8 What is the Communication Plan in HL7 wrt the Status of Requests
- 9 When
- 10 Where
How is it Determined When a Content Change for SNOMED- is Needed?
- Replacing HL7 internally created and curated content. (i.e. When an existing HL7 value set (or a constraint) is converted to SNOMED-CT content)
- Is all or part of this content request contained in within SNOMED? - ADD TO HARMONIZATION CHECKLIST?
- When a value set is proposed that is only partially covered by SNOMED-CT and the requestor is a licensed SNOMED-CT user but does not have a national release center (i.e. if you have a national release center that is the organization to which applications for code extensions should be made).
How is it Determined that a Given Request is Valid for Submission?
- Is the content domain valid for SNOMED
- Is the request provided in such a way that the intent of the request can be ascertained?
- Is there a justification or rationale provided for the content request?
- Is the content request of the appropriate granularity?
- Is the requested content parent in the appropriate SNOMED hierarchy?
- Is the content requested in the appropriate location within the hierarchy? (i.e. does an appropriate parent concept exist?)
- Does the concept already exist in SNOMED?
- Is the requested content a synonym for an existing concept?
- Is the requested content change ambiguous?
- Are there at least two Realms that will support the proposed content change request?
How are Request Submissions Packaged?
- CONSIDERATION: "Related" content changes should be packaged together and submitted as a whole.
- CONSIDERATION: Multiple unrelated content changes should be submitted separately
- CONSIDERATION: Should HL7 obtain its own SNOMED namespace?
Who within HL7 can Request a SNOMED Submission
Who within HL7 can Submit a SNOMED Submission
Who within HL7 is responsible for Managing SNOMED Submissions
Who can Validate Domain Specific Requests?
- Clinical review is necessary to validate content.
What is the Communication Plan in HL7 wrt the Status of Requests
- If content change requests are rejected, how to communicate the information to the proponent to ensure it the change request is captured in the proponent's international extension?
