You know how tracing macros limit you to 32 fields?

That's not true anymore, and hasn't been for over a year! With tracing-core 0.1.32 and tracing 0.1.40 you can have as many fields as you damn well please.

github.com/tokio-rs/tra...

#rust #rustlang #tracing

it bothers me when people say "it was a different time"

idgaf and i won't support it out of personal valuesets that i worked hard to be consistent with, regardless of the time period

The actual Terminology Server is still up. May just be a local thing on the browser. I had not heard about the deprivation. I have a load of valuesets on there so would need to plan (although we do have something in development)

I really enjoy reading the expanding literature on #invariance of #ValueSets. Two interesting papers and a taxonomy regarding #obsolescence

1- link.springer.com/article/10.1...

2- www.sciencedirect.com/science/arti...

3- link.springer.com/article/10.1...

#HealthEconomics
#EQ5D #Psychometrics

The terminology server itself has a FHIR interface. You can use Shrimp or Snapper and can apply for API key and use whatever language you want with FHIR library. It is a server rather than public facing. I built (with AI) a page of our unit's valuesets based on that back end. snomed.gpcontract.co.uk

A misclassified medication in a value set led to a clinical decision support alert recommending an unnecessary beta-blocker, resulting in patient harm and hospitalization. www.medrxiv.org/content/10.1...

#ValueSets #Interoperability #HealthcareIT

Inaccurate value sets can create invisible risk. When value sets aren’t actively maintained, the impact can reach far beyond what anyone expects. Watch the slides below to see how our experts break down one example. www.medrxiv.org/content/10.1...

#ValueSets #Interoperability