See: string.context.jsonld for an example. The value tags for all primitive types should be the same:

  "value": {
      "@id": "fhir:value",
      "@type": "http://www.w3.org/2001/XMLSchema#string"
    },

(not "@id": "fhir.string.value",)

FHIR attributes that reference attributes defined elsewhere in the model are not being generated in the contexts. As an example the detail and additem.adjudication elements from ClaimResponse:

Should produce the following in the JSON-LD

   "noteNumber": {
      "@id": "fhir:ClaimResponse.addItem.noteNumber",
      "@context": "positiveint.context.jsonld"
    },
    "detail": {
      "@id": "fhir:ClaimResponse.addItem.detail",
      "@context": "claimresponse.additem.detail.context.jsonld"
    },
    "adjudication": {
      "@id": "fhir.ClaimResponse.addItem.adjudication",
      "@context": "claimresponse.adjudication.context.jsonld"
    },

Wherever we generate the new context we need to either:
a) emit an official one along with other contexts
-- or --
b) determine whether this is actually needed and, if not, merge it into the basic build

Replace the namespace lines in the root contexts with:

"@imports": "root.context.jsonld",

This will allow us to maintain a complete set of namespaces for the FHIR context.

Add root.context.jsonld to the output directory or some other well known location.

"@​context": {
  "@​version": 1.1,
  "@​vocab": "http://example.com/UNKNOWN#",
  "xsd": "http://www.w3.org/2001/XMLSchema#",
  "fhir": "http://hl7.org/fhir/",
  "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
  "id": {

contextFiles/patient.context.jsonld has the following:

 "contact": {
      "@id": "fhir:Patient.contact",
      "@context": "patient.contact.context.jsonld"
    },

But there is no contextFiles/patient.contact.context.jsonld on the server?

Hi, firstly thanks for this project it is great work! I work in the Credentials Community Group working with technologies like W3C Verifiable Credentials and as of recent there has been much interest in applications of the technology for vaccination certificates. As a result I have begun the initiative to define a vocabulary for this purpose however ideally we would like to leverage more existing ontologies like HL7 FHIR so are open to redefining terms in the vocab to suit this and I believe we could leverage some of the great work you guys have done to date to accomplish this?

A couple of quick questions w.r.t your work

1. How actively is the ontology maintained and how complete is it? It would be great to know this in reference to both R4 and R5
2. It appears the current IRIs the context uses are not resolvable i.e I get a 404 on http://hl7.org/fhir/Patient.gender

Both the R4 and R5 context generators have encountered problems in the https://github.com/fhircat/org.hl7.fhir.core. We have built a branch (LDContextGenerator-merge) to address the R5 issues:

cd org.hl7.fhir.r5
mvn -e -Dtest=org.hl7.fhir.r5.test.LDContextGeneratorTests test

But are unable to do a corresponding build on the existing FHIR R4 data.

The JSON-LD context generator is currently building into ~/LDContext/R4/R5. We need to enhance the script to build the contexts locally and then to zip them up into some well known/documented place