lawley

Comparisons with Ontoserver MMS CodeSystem

$lookup and metadata

Fact	WHO (id.who.int FHIR)	Comparator
CapabilityStatement.fhirVersion	5.0.0	4.0.1
CodeSystem ops declared	lookup, validate-code	batch-validate-code, diff, find-matches, lookup, meta, meta-add, meta-delete, subsumes, validate, validate-code, x-upload-external
MMS CodeSystem present		true
MMS CodeSystem.content	not-present	complete

lawley

Parameterised ValueSets V0.2

Background and Motivation

A common activity in a data entry scenarion like a Questionnaire is to have the set of available options for one question depend on an answer to another question. For example, after choosing a country, the set of available options for a question about a state or region would depend on the chosen country. Ideally a ValueSet would be bound to the state/region question, but since it needs to be pre-defined we cannot have one that is sensitive to the country.

Similar examples exist when questions correlating diagnoses or procedures and body sites/regions, or medications, or tests.

lawley

import type { CodeableConcept, Coding, OperationOutcome, OperationOutcomeIssue, Reference, Resource } from "fhir/r4b";
import fhirpath from "fhirpath";
import { logMessage, CreateOperationOutcome } from "~/utils/create-outcome";

// --------------------------------------------------------------------------
// The concept of this POC is to demonstrate an approach to perform some
// async based methods as functions inside the fhirpath engine without
// converting the entire engine to process things asynchronously.
// e.g. Terminology functions such as memberOf, subsumes, or resolve()
//

lawley

ConceptMap moving from R4 to R5

ConceptMap Resource

As of FHIR R4, ConceptMap is still a relatively immature resource. Some evidence of this is in the current state of the proposed R5 changes that:

1. refine the set of valid relationship codes,
2. explicitly broaden its scope beyond equivalence relationships, and
3. re-structure handling of noMap.

lawley

version: "2"
services:
  onto:
    image: "aehrc/ontoserver"
    links:
    - "db" 
    ports:
    - "8080:80" 

  db:

lawley

Experiment with dendrogram of graph (cf tree)

A dendrogram is a node-link diagram that places leaf nodes of the tree at the same depth. In this example, the classes (leaf nodes) are aligned on the right edge, with the packages (internal nodes) to the left. Data shows the Flare class hierarchy, courtesy Jeff Heer.

Compare to this radial layout.