Page tree
Skip to end of metadata
Go to start of metadata

Scope

This page collects some initial thoughts about the FHIR4FAIR FHIR IG

To be discussed

  1. Structure of the guide
  2. Extension of the "informative" part 
  3. Proposed development approach
  4. Organization of a FAIR track ?

Structure of the guide


Proposed development approach

FAIR data object is a quite wide concept that could cover very different things of real life: from a collection of data (data set) to a single atomic information (e.g. a diagnosis).

Depending of what is a "FAIR object"  the boundary between data and metadata may change; including how the "object" could be represented in FHIR and instances assessed.

The suggestion to be discussed with the team is the therefore the following:

  • identify relevant types of FAIR objects for health data in real life (to be determined how many and which one)
    • the guide is restricted to social and health data, other kinds of health-related artefacts, as clinical guidelines, algorithms, software, models are out of scope. 
  • select one of them as reference case and focus on that kind of object
  • identify a minimal set of information that are relevant in real life for the components of that FAIR object.
  • proceed incrementally starting from few essential information, in order to excursive also the development process (i.e. not to try to cover everything from the beginning)


The following picture shows one proposed conceptual structure of a FAIR data object , (another representation includes the provenance in the metadata and add as a separate component "standards and code")


hereafter a preliminary draft of types of objects we may be interested to consider as starting point, suggesting to start with data collections.




  • No labels

4 Comments

  1. Regarding FAIR PID, we must consider that what we specify in the Guide complies with EOSC's PID policy (https://ec.europa.eu/info/sites/info/files/research_and_innovation/ki0420576enn-updt.pdf)

  2. With respect to changing the name of "FAIR resource", this term is used with another meaning in the EOSC Interoperability Framework Specification v1.0. In fact it uses an example from ISO 11179 that maps to FHIR. But the term resource is not used for information, but for those tools that help (vocabulary services, etc...). I don't know if a FAIR resource is just a composition of elements (similar to the ISO13606 structure).

    1. What I'd like to highlight is that in our mapping to FHIR we should consider the fact that there are different kinds of objects; and that we need to classify them somehow.


      Not sure if this classification is the right one, but is there for our discussion..

      About the "FAIR resource" name I don't like it too ; but I have not been able so far to come up with a right term ... so suggestions are welcome :-)

  3. Finally, I propose to focus on the conformance criteria, as voted in the abstention.