Page tree

1. NEW
All submissions to authoring tool will start with a status of NEW. A customer submits a request, which can be a single editing request or a batch status change for large numbers of new requests.
The possible changes include:

  • Add new concept
  • Add new relationship
  • Add new synonym
  • Add parent
  • Change description
  • Change parent
  • Change relationship
  • Retire Concept
  • Retire Description
  • Retire Relationship
  • Other


2. ACCEPTED
If the request meets the criteria to be in scope for the international release of SNOMED CT then status will be changed to the ACCEPTED. An author who is in charge to manage requests goes through requests and accepts the request, which falls into the scope of SNOMED CT International Release. After request is accepted, a notification should be sent to the customer so that she/he knows the request is accepted. Manager assigns the accepted requests to herself/himself or another author. Author should be able to transfer her/his requests to another author if she/he needs to.


3. IN PROGRESS
When an author (Editor) starts making the requested change to SNOMED CT, the status will be changed to the IN PROGRESS. At this status, the editing author needs to do research regarding inclusion of the requested change. It is useful to record resources that have been used to research the request. A notification should be sent to customer so that she/he knows an author has been working her/his request.


4. ON HOLD
When a new request aligns with an open project, it may be necessary to place the request on hold until editorial policy is available to support the requested change or addition. The status will be changed to ON HOLD. A notification should be sent to customer so that she/he knows the request is on hold for editorial policy is available.
After the editorial policy made for the project, the Editor will work on the request. The status will be changed to IN PROGRESS (Section 3).


5. REJECTED
If the request does not fit in scope of the SNOMED CT International Release or the request was not well defined, then the request will be rejected. The status will be changed to REJECTED. A notification includes reason of rejection should be sent to the customer so that she/he knows the request is rejected.


6. FORWARDED
If the request does not fit in scope of the SNOMED CT International Release but fits in the SNOMED CT regional extension, then the request will be forwarded to the regional release centre. The status will be changed to FORWARDED.


7. CLARIFICATION
If the request was not well defined by customer, then author will ask customer to make a clarification. The status will be changed to CLARIFICATION.


8. PEER REVIEW
When another author (Reviewer) starts reviewing the requested change(s) made by the editing author, the status will be changed to PEER REVIEW. A notification should be sent to customer so that she/he knows an author has been reviewing her/his requested change in SNOMED CT.
If Reviewer does not agree with Editor's changes, then Reviewer requires Editor to make further changes. The status will be changed from the PEER REVIEW to the IN PROGRESS (Section 3).
If both Reviewer and Editor do not agree that the concept is in the scope of SNOMED CT International Release in review, then the status will be changed from the PEER REVIEW to the REJECTED (Section 5).


8. ESCALATION REVIEW
If Editor and Reviewer have conflict on the requested change and they cannot resolve it during PEER REVIEW (Section 8), then it goes to the status of ESCALATION REVIEW. The ESCALATION REVIEW is during Authoring team's bi-weekly meeting. In the ESCALATION REVIEW, authors discuss requests that Editor and Reviewer had conflict on.
If authoring team agrees with Editor's change, then change will be approved. The status will be changed to APPROVED (Section 10).


9. EDITORIAL PANEL DISCUSSION
If the conflict cannot be resolved during the ESCALATION REVIEW (Section 8), the request will be discussed at EDITORIAL PANEL. The status will be changed to EDITORIAL PANEL DISCUSSION.
If Editorial Panel decided to reject the request because they do not agree that the requested change is fit in the scope of SNOMED CT, then they reject the request. The status will be changed to REJECTED (Section 5).
If Editorial Panel suggested some modifications on the change made by Editor, then the status will be changed to IN PROGRESS (Section 3).
If Editorial Panel agreed with Editor's change, then the status will be changed to APPROVED (Section 10).


10. APPROVED
After the requested change approved by PEER REVIEW, ESCALATION REVIEW, or EDITORIAL PANEL REVIEW, the status will be changed to APPROVED.


11. READY FOR RELEASE
All approved requests are transferred to the READY FOR RELEASE server. The status will be changed to READY FOR RELEASE.


12. RELEASE QUALITY ASSURANCE
The Editorial Panel runs the final quality assurance review. If there is any request need a further editing, the request will go back to the Editor. The status will be changed to IN PROGRESS (Section 3).


13. APPEAL
When a request has been rejected and the customer wishes to have a further review of the requested change, the customer may instigate the status of APPEAL. Appealed request will be reviewed and discussed at Editorial Panel Discussion. The status will be changed to EDITORIAL PANEL DISCUSSION (Section 9).


14. WITHDRAWNA customer may choose to withdraw their original request at any time, the status will be changed to WITHDRAWN.





  • No labels