Hello - I'd also like to add code 58 'Non-residential Opioid Treatment Facility' to the list

Dear Meghan, thanks for letting us know about the missing Revenue Codes. I trust that you have turned every stone and collected all missing codes? This vocabulary hasn't been updated for a while.
Having said that, we take this request into consideration (it is not a lot of work), but it is rather low priority (as opposed to fixing a really nasty bug). We will try to sneak that into one of the next vocabulary releases but still ask for a little patience.
The code "58" you mentioned. Would that be "0058-Non-residential Opioid Treatment Facility", following the notation of the other codes?
Thank you!

Dear @MNairn , we came back to your request. Thanks again for bringing this up. When trying to find a more recent version of the revenue codes, we realized that they are under license by NUBC at the moment, so we are trying to figure out a way to get an updated version. As of your request for "58 'Non-residential Opioid Treatment Facility'", this seems to be an addition to the CMS POS (Place of Service), not a UB04 Revenue Code, right?

Hi @MNairn , please find attached a spreadsheet with an update list and some sources. I have tried to look at 3 different possible sources, but could not find a comprehensive up to date list. Your input was definitely the most valuable. Can you take a look and most importantly let us know if we should include the codes for "RUGS" (9000-9044)?
UB04-Revenue Code update2010-20.xlsx
Thanks!

Hi @MNairn - apologies for the long silence. We were very close to finalize the work on Revenue Codes and additional CMS Place of Service codes when we realized that we have a "code re-use" for both. Revenue Codes has reused codes 891 and 892 with a different meaning and the latest CMS PoS update has tampered with their code 02 which went from Telehealth to "Telehealth - Provided Other than in Patient’s Home". This actually causes us some pain as we would now have to address a temporal validity and there are a couple of conventions to be observed. For example, the previous concepts would have to become invalid and also non-standard which makes it impossible to keep using them as a proper target. Unfortunately, there is no proper replacement target and we would have to build one manually. Based on validity within a particular time period, the ETL would have to observe which target to map to...
We are still discussing possible solutions for this and will keep you updated here.
Thanks ~ Mik