I am adding lateralised content to 232086000 |Neovascular glaucoma (disorder)| however I wanted to check the current descriptions on this concept are correct:
Powered by a free Atlassian Confluence Community License granted to SNOMED International. Evaluate Confluence today.
6 Comments
Elaine Wooler
In addition there is another concept that reflect open-angle - 1111401000000105 |Open angle glaucoma due to neovascularization (disorder)|
Eric Brown
We usually think of neovascular glaucoma as being a secondary cause of angle closure glaucoma. I guess while it's possible that it could be associated with an open angle, I don't believe that it's common enough to warrant its own term. If someone thought that they had a patient with NVG and an open angle, they could instead use an open angle term and a neovascular finding (such as neovascularization of the iris).
Ian Rodrigues
Thanks Elaine Wooler - agree it would be best to rename Neovascular Glaucoma to Neovascular angle closure glaucoma, especially if Open angle glaucoma due to neovascularisation already exists. Many thanks!
Eric Brown
The downside is that people almost always call this "neovascular glaucoma" or NVG. At least in Pubmed, there are hundreds of articles related to "neovascular glaucoma" and absolutely no references with the phrase "neovascular angle closure glaucoma".
Since NVG almost exclusively refers to a closed angle glaucoma, I'd prefer to keep the term (and consider retiring the open-angle term unless someone thinks that it's commonly used).
Ian Rodrigues
Good point! We could discuss more on the call this evening.
Elaine, presumably both terms could coexist with the same SNOMED code as synonymous terms? Certainly in terms of mapping, neovascular glaucoma should set in the angle closure section.
Anthony Khawaja
Let's discuss tonight, but I definitely see my fair share of neovascular OAG - there's a very fine sheet of NVA that many people miss if not using a high magnification gonio. In fact I think this is underdiagnosed, and if a definite entity, it should have it's own code (we want a code for every distinct entity, not just common ones). Perhaps we can have a hierarchy, with OAG and ACG variants being under a more general term? Let's discuss! Thanks all