Place to prepare proposal to FHIR about JSON, JSON-Schema, Swagger/OpenAPI, JSON native databases and other JSON-frendly formats (yaml, edn, avro, protobuf etc) and technologies
Switch branches/tags
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
CODE_OF_CONDUCT.md
CONTRIBUTING.md
FHIR_JSON2.md
LICENSE
README.md
issue_template.md

README.md

FHIR fuel

Place to prepare proposals to FHIR standard about JSON, JSON-schema, Swagger/OpenAPI integration, native JSON databases and other JSON-like formats (yaml, avro, edn).

Motivation

Design of FHIR formats, to be honest, was essentially driven by XML and Object Oriented implementations. Not so much attention was given to design idiomatic JSON format. JSON and other JSON like formats like yaml, edn, avro are very popular in avantе-garde of programmers, some modern databases now could understad JSON as first-class data-structures, that’s why we think, good design for it is strictly required for FHIR adoption.

TODO

  • Use issues to start discussion of relevant ideas.
  • We could dump some consensus into repository as some artifacts.
  • Informal rules could be formulated in wiki.
  • Create stream in https://chat.fhir.org (integrate github)
  • Live discussions using youtube/hangout