John Grimes

John Grimes

@john-grimes.bsky.social

Health tech, health data analytics. I make Pathling šŸ”„āœØ

14 followers39 following18 posts

I'm bringing this poster along to the SNOMED CT Expo in Sydney on Wednesday. The QR code is a SMART Health Link to a FHIR Questionnaire. A token in the link sends your answers back to a FHIR server, with no login. Fill it in in your browser, or in Platypus (see Kyle Pettigrew) with your own data.

The R port of fhir-tx-encoder is out: turn SNOMED CT codes into ML features via a FHIR terminology server. Multi-hot sparse matrix, subsumption ancestors, a tidymodels recipes step, same output as the Python lib. github.com/aehrc/fhir-t...

github.comGitHub - aehrc/fhir-tx-encoder: A tool for encoding FHIR terminology concepts for machine learning applications.A tool for encoding FHIR terminology concepts for machine learning applications. - aehrc/fhir-tx-encoder

John Grimes reposted

Replying to @john-grimes.bsky.social

UPDATE: I'm now in the lead! Sorry Shane! I'm not used to the AU edition, and am based in UK so there's been a serious learning curve on many of the questions... but the `sct` toolkit coped with its first non-UK SNOMED edition test without any problems. github.com/pacharanero/...

github.comGitHub - pacharanero/sct: SNOMED-CT tooling, brought into the 21stC. RF2 → NDJSON → SQLite | Vector | .arrow, | .parquet | .md | refsets | .codelist | MCP | CTV3 & ReadV2 - readySNOMED-CT tooling, brought into the 21stC. RF2 → NDJSON → SQLite | Vector | .arrow, | .parquet | .md | refsets | .codelist | MCP | CTV3 & ReadV2 - ready - pacharanero/sct
View full thread

`$jobs` lists the asynchronous jobs on the server: the operation that started each one, its status, progress, and the URL to poll or cancel it. With authorisation on, a caller sees only their own. The admin UI has a matching page, so an operator can stop a runaway query.

SQLView Libraries are named SQL table sources, stored on the server and referenced by canonical URL. A cohort filter or a derived column is written once, then read by any number of queries and views. Change the definition and every dependent query picks it up on its next run.

`$sql-export` carries any number of subjects in one job, in any mixture of ViewDefinitions, SQLQueries and SQLViews. Each reads the Delta table versions pinned when the job began, so a write that lands mid-job is invisible to all of them. NDJSON, CSV or Parquet, one file per subject.

You are up to date.