SnoMAP Webservice Usage Guide
This guide is for use with the snoMAP Starter Web Service. These usage tips should be used in conjunction with the advice provided in the Terminology Map Implementation Guide
1. Input file
The input file is required to be a csv file with SNOMED CT-AU Concept ID’s listed with NO header.
1.1. Clean your data
- Please note that Description ID’s will not be processed through the Web Service Tool. The difference between Concept and Description ID’s can be found by looking at your IDs:
| Description IDs will have the penultimate digit of “1” | 474280013 |
| Concept IDs will have the penultimate digit of “0” | 128045006 |
If your data has Description ID’s you will need to convert these to Concept ID’s as part of the data preparation process. This can be done using the RF2 files imported into a SQL database, or similar table structure, and retrieving the corresponding Concept ID for each of your Description IDs matched in the description table.
- Whenever you are dealing with the use of Microsoft Excel it is advised that the ID column be formatted as text/string to avoid Excel converting them to scientific numbers and truncating the long identifiers.
2.Evaluate your ‘No Match’ Results
Once you have uploaded and translated your file, you will receive the output file and may find that you have a number of items with ‘No Match’ in the ICD column. Analysis of why you have received No Matches will then be required.
No Match content will give an indication of data quality collected in the Information System and could provide feedback to assist with improvements to Clinical Information Systems and Staff training.
2.1. Evaluate valid SNOMED CT concept IDs
- If the ID’s are valid SNOMED CT concept codes you can use the SHRIMP tool to investigate, or create SQL queries to retrieve concept information such as the PT, FSN and Hierarchy information to help you evaluate why they have a No Match.
- If the ID’s are valid SNOMED CT concept codes they may show that the data entry selection of codes has been done outside the scope of the map. Some Information Systems have challenges limiting data entry scope to clinical findings and this is maybe where this has come from. Some examples of these types of No Match codes are listed below with examples of how you might evaluate if there are applicable SNOMED CT-AU concepts that can be included in your data. It may be possible to replace codes that were originally recorded if the meaning and intention of the user is clear, based on the context. This should be done with care and if any changes are made, it is important to keep a record of the original code selected, the changed code and all assumptions you have made.
| Concept ID | FSN | Reason |
| 3821009 | Blunt injury (morphologic abnormality) | Out of scope – from invalid hierarchy- applicable code may be: 425359009 Blunt injury (disorder) |
| 12856003 | Uneven venous ectasia (morphologic abnormality) | Out of scope – from invalid hierarchy- applicable code may be: 128060009 Venous varices (disorder) |
| 18126004 | Diverticulitis (morphologic abnormality) | Out of scope – from invalid hierarchy- applicable code may be: 307496006 Diverticulitis (disorder) |
| 53041004 | Alcohol (substance) | Out of scope – from invalid hierarchy – applicable code may be: 25702006 Alcohol intoxication (disorder) |
| 135877001 | Stroke risk (assessment scale) | Out of scope – from invalid hierarchy – applicable code may be: 866240007 At risk of cerebrovascular accident (finding) |
2.2. ID’s are NOT valid SNOMED CT concept IDs
- If the ID’s are Description ID’s: See section 1.1 Clean your data
- If the ID’s are valid not SNOMED CT concept codes they will not be able to be mapped and will have to be excluded from your data sample.
3. Re-map your corrected ‘No Match’ concepts.
Once you have evaluated your No Match items and identified suitable SNOMED CT-AU concepts you can re-run these through the Web Service Tool and receive the translated output file for your use.