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




1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact being Reaffirmed or proceeding to Normative directly after being either Informative or STU?

No

1e. Today's Date

1f. Name of standard being reaffirmed

1g. Project Artifact Information

1h. ISO/IEC Standard to Adopt

1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption?

1j. Unit of Measure

2a. Primary/Sponsor WG

Service Oriented Architecture

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts.
FHIR-I would like to be kept informed of progresses.
ArB would like to be kept informed of progresses.

2f. Modeling Facilitator

2g. Publishing Facilitator

Giorgio Cangioli

2h. Vocabulary Facilitator

2i. Domain Expert Representative

Oya Beyan (Fraunhofer, RDA DE; EOSC FAIR WG); Carlos Luis Parra Calderón (EOSC; FAIR4Health coordinator; Andalusian Health); Catherine Chronaki (HL7 Europe); ALICIA MARTINEZ GARCIA (Andalusian Health Service); Anthony Juehne (RDA Reproducible Health Services WG ); Matthias Löbe (IMISE Leipzig)

2j. Business Requirements Analyst

2k. Conformance Facilitator

Giorgio Cangioli

2l. Other Facilitators

2m. Implementers

1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to (FAIR Principles https://www.go-fair.org/fair-principles):
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part addressing the above mentioned points and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.

This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

Attachments

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles (https://www.go-fair.org/fair-principles/)
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3d. External Drivers

3e. Objectives/Deliverables and Target Dates

Connect-a-thon [Jan 2021]
Connect-a-thon [May 2021]
STU ballot [May 2021]
Publication as STU IG (2 years) [Oct 2021]
Normative ballot [May 2023]
Publication as Normative IG [Oct 2023]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3g. Lineage

3h. Project Dependencies

3i. HL7-Managed Project Document Repository URL:

.

3j. Backwards Compatibility

No

3k. Additional Backwards Compatibility Information (if applicable)

3l. Using Current V3 Data Types?

N/A

3l. Reason for not using current V3 data types?

3m. External Vocabularies

Unknown

3n. List of Vocabularies

3o. Earliest prior release and/or version to which the compatibility applies

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

4c. FHIR Profiles Version

4d. Please define your New Product Definition

4d. Please define your New Product Family

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. White Paper Type

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Externally developed IG is to be (select one)

5a. Specify external organization

RDA

5a. Revising Current Standard Info

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

5d. Joint Copyright

No

5e. I understand I must submit a Joint Copyright Letter of Agreement to the TSC in order for the PSS to receive TSC approval.

no

6a. External Project Collaboration

RDA

6b. Content Already Developed

0%

6c. Content externally developed?

No

6d. List Developers of Externally Developed Content

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs)

6f. Other Stakeholders

6g. Vendors

EHR, PHR, Health Care IT

6g. Other Vendors

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6h. Other Providers

6i. Realm

Universal

7d. US Realm Approval Date

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Sep 22, 2020

7c. Co-Sponsor Approval Date

7c. Co-Sponsor 2 Approval Date

7c. Co-Sponsor 3 Approval Date

7c. Co-Sponsor 4 Approval Date

7c. Co-Sponsor 5 Approval Date

7c. Co-Sponsor 6 Approval Date

7c. Co-Sponsor 7 Approval Date

7c. Co-Sponsor 8 Approval Date

7c. Co-Sponsor 9 Approval Date

7c. Co-Sponsor 10 Approval Date

7e. CDA MG Approval Date

7f. FMG Approval Date

Sep 30, 2020

7g. V2 MG Approval Date

7h. Architecture Review Board Approval Date

7i. Steering Division Approval Date

7j. TSC Approval Date



 Show Changes

Version

20

Modifier

Giorgio Cangioli

Modify Date

Oct 29, 2020 20:16

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts.
FHIR-I would like to be kept informed of progresses.
ArB would like to be kept informed of progresses.

2g. Publishing Facilitator

Giorgio Cangioli

2i. Domain Expert Representative

Oya Beyan (Fraunhofer, RDA DE; EOSC FAIR WG); Carlos Luis Parra Calderón (EOSC; FAIR4Health coordinator; Andalusian Health); Catherine Chronaki (HL7 Europe); ALICIA MARTINEZ GARCIA (Andalusian Health Service); Anthony Juehne (RDA Reproducible Health Services WG ); Matthias Löbe (IMISE Leipzig)

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to (FAIR Principles https://www.go-fair.org/fair-principles):
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part addressing the above mentioned points and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.

This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles (https://www.go-fair.org/fair-principles/)
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Connect-a-thon [Jan 2021]
Connect-a-thon [May 2021]
STU ballot [May 2021]
Publication as STU IG (2 years) [Oct 2021]
Normative ballot [May 2023]
Publication as Normative IG [Oct 2023]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3i. HL7-Managed Project Document Repository URL:

.

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

STU to Normative

5d. Joint Copyright

No

6a. External Project Collaboration

RDA

6b. Content Already Developed

0%

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Sep 22, 2020

7f. FMG Approval Date

Sep 30, 2020

Version

19

Modifier

Giorgio Cangioli

Modify Date

Oct 01, 2020 11:02

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG

Architecture Review Board

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts.
FHIR-I would like to be kept informed of progress.

2g. Publishing Facilitator

Giorgio Cangioli

2i. Domain Expert Representative

Oya Beyan (Fraunhofer, RDA DE; EOSC FAIR WG); Carlos Luis Parra Calderón (EOSC; FAIR4Health coordinator; Andalusian Health); Catherine Chronaki (HL7 Europe); ALICIA MARTINEZ GARCIA (Andalusian Health Service); Anthony Juehne (RDA Reproducible Health Services WG ); Matthias Löbe (IMISE Leipzig)

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to (FAIR Principles https://www.go-fair.org/fair-principles):
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part addressing the above mentioned points and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.

This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles (https://www.go-fair.org/fair-principles/)
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Connect-a-thon [Jan 2021]
Connect-a-thon [May 2021]
STU ballot [May 2021]
Publication as STU IG (2 years) [Oct 2021]
Normative ballot [May 2023]
Publication as Normative IG [Oct 2023]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3i. HL7-Managed Project Document Repository URL:

.

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

STU to Normative

5d. Joint Copyright

No

6a. External Project Collaboration

RDA

6b. Content Already Developed

0%

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Sep 22, 2020

7f. FMG Approval Date

Sep 30, 2020

Version

18

Modifier

Giorgio Cangioli

Modify Date

Oct 01, 2020 11:01

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG

Architecture Review Board

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts.
FHIR-I would like to be kept informed of progress.

2g. Publishing Facilitator

Giorgio Cangioli

2i. Domain Expert Representative

Oya Beyan (Fraunhofer, RDA DE; EOSC FAIR WG); Carlos Luis Parra Calderón (EOSC; FAIR4Health coordinator; Andalusian Health); Catherine Chronaki (HL7 Europe); ALICIA MARTINEZ GARCIA (Andalusian Health Service); Anthony Juehne (RDA Reproducible Health Services WG ); Matthias Löbe (IMISE Leipzig)

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to (FAIR Principles https://www.go-fair.org/fair-principles):
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part addressing the above mentioned points and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.

This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles (https://www.go-fair.org/fair-principles/)
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Connect-a-thon [Jan 2021]
Connect-a-thon [May 2021]
STU ballot [May 2021]
Publication as STU IG (2 years) [Oct 2021]
Normative ballot [May 2023]
Publication as Normative IG [Oct 2023]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3i. HL7-Managed Project Document Repository URL:

.

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

STU to Normative

5d. Joint Copyright

No

6a. External Project Collaboration

RDA

6b. Content Already Developed

0%

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Sep 22, 2020

Version

17

Modifier

Giorgio Cangioli

Modify Date

Sep 28, 2020 19:49

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG

Architecture Review Board

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts.
FHIR-I would like to be kept informed of progress.

2g. Publishing Facilitator

Giorgio Cangioli

2i. Domain Expert Representative

Oya Beyan (Fraunhofer, RDA DE; EOSC FAIR WG); Carlos Luis Parra Calderón (EOSC; FAIR4Health coordinator; Andalusian Health); Catherine Chronaki (HL7 Europe); ALICIA MARTINEZ GARCIA (Andalusian Health Service); Anthony Juehne (RDA Reproducible Health Services WG ); Matthias Löbe (IMISE Leipzig)

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to (FAIR Principles https://www.go-fair.org/fair-principles):
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part addressing the above mentioned points and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.

This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles (https://www.go-fair.org/fair-principles/)
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Connect-a-thon [Jan 2021]
Connect-a-thon [May 2021]
STU ballot [May 2021]
Publication as STU IG (2 years) [Ott 2021]
Normative ballot [May 2023]
Publication as Normative IG [Ott 2023]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3i. HL7-Managed Project Document Repository URL:

.

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

STU to Normative

5d. Joint Copyright

No

6a. External Project Collaboration

RDA

6b. Content Already Developed

0%

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Sep 22, 2020

Version

16

Modifier

Giorgio Cangioli

Modify Date

Sep 26, 2020 09:03

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG

Architecture Review Board

2b. Co-Sponsor WG 2

FHIR Infrastructure

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts

2g. Publishing Facilitator

Giorgio Cangioli

2i. Domain Expert Representative

Oya Beyan (Fraunhofer, RDA DE; EOSC FAIR WG); Carlos Luis Parra Calderón (EOSC; FAIR4Health coordinator; Andalusian Health); Catherine Chronaki (HL7 Europe); ALICIA MARTINEZ GARCIA (Andalusian Health Service); Anthony Juehne (RDA Reproducible Health Services WG ); Matthias Löbe (IMISE Leipzig)

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to (FAIR Principles https://www.go-fair.org/fair-principles):
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part addressing the above mentioned points and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.


This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles (https://www.go-fair.org/fair-principles/)
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Informative ballot (the ballot version may include conformance resources and examples; for exemplification purposes) [May 2021]
Connect-a-thon [May 2021]
Comment reconciliation [May-Ago 2021]
Publication as Informative IG [Sept 2021]
Connect-a-thon [Sept 2021]
STU ballot [Jan 2022]
Publication as STU IG (2 years) [Apr 2022]
Normative ballot [May 2024]
Publication as Normative IG [Sept 2024]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3i. HL7-Managed Project Document Repository URL:

.

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

Informative, STU to Normative

5d. Joint Copyright

No

6a. External Project Collaboration

RDA

6b. Content Already Developed

0%

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Sep 22, 2020

Version

15

Modifier

Giorgio Cangioli

Modify Date

Sep 22, 2020 22:35

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG

Architecture Review Board

2b. Co-Sponsor WG 2

FHIR Infrastructure

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts

2g. Publishing Facilitator

Giorgio Cangioli

2i. Domain Expert Representative

Oya Beyan (Fraunhofer, RDA DE; EOSC FAIR WG); Carlos Luis Parra Calderón (EOSC; FAIR4Health coordinator; Andalusian Health); Catherine Chronaki (HL7 Europe); ALICIA MARTINEZ GARCIA (Andalusian Health Service); Anthony Juehne (RDA Reproducible Health Services WG ); Matthias Löbe (IMISE Leipzig)

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to (FAIR Principles https://www.go-fair.org/fair-principles):
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part addressing the above mentioned points and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.


This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles (https://www.go-fair.org/fair-principles/)
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Informative ballot (the ballot version may include conformance resources and examples; for exemplification purposes) [May 2021]
Connect-a-thon [May 2021]
Comment reconciliation [May-Ago 2021]
Publication as Informative IG [Sept 2021]
Connect-a-thon [Sept 2021]
STU ballot [Jan 2022]
Publication as STU IG (2 years) [Apr 2022]
Normative ballot [May 2024]
Publication as Normative IG [Sept 2024]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

Informative, STU to Normative

5d. Joint Copyright

No

6a. External Project Collaboration

RDA

6b. Content Already Developed

0%

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

14

Modifier

Giorgio Cangioli

Modify Date

Sep 22, 2020 22:34

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG

Architecture Review Board

2b. Co-Sponsor WG 2

FHIR Infrastructure

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts

2g. Publishing Facilitator

Giorgio Cangioli

2i. Domain Expert Representative

Oya Beyan (Fraunhofer, RDA DE; EOSC FAIR WG); Carlos Luis Parra Calderón (EOSC; FAIR4Health coordinator; Andalusian Health); Catherine Chronaki (HL7 Europe); ALICIA MARTINEZ GARCIA (Andalusian Health Service); Anthony Juehne (RDA Reproducible Health Services WG ); Matthias Löbe (IMISE Leipzig)

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to:
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part addressing the above mentioned points and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.


This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Informative ballot (the ballot version may include conformance resources and examples; for exemplification purposes) [May 2021]
Connect-a-thon [May 2021]
Comment reconciliation [May-Ago 2021]
Publication as Informative IG [Sept 2021]
Connect-a-thon [Sept 2021]
STU ballot [Jan 2022]
Publication as STU IG (2 years) [Apr 2022]
Normative ballot [May 2024]
Publication as Normative IG [Sept 2024]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

Informative, STU to Normative

5d. Joint Copyright

No

6a. External Project Collaboration

RDA

6b. Content Already Developed

0%

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

13

Modifier

Giorgio Cangioli

Modify Date

Sep 22, 2020 22:16

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG

Architecture Review Board

2b. Co-Sponsor WG 2

FHIR Infrastructure

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts

2g. Publishing Facilitator

Giorgio Cangioli

2i. Domain Expert Representative

Oya Beyan (Fraunhofer, RDA DE; EOSC FAIR WG); Carlos Luis Parra Calderón (EOSC; FAIR4Health coordinator; Andalusian Health); Catherine Chronaki (HL7 Europe); ALICIA MARTINEZ GARCIA (Andalusian Health Service); Anthony Juehne (RDA Reproducible Health Services WG ); Matthias Löbe (IMISE Leipzig)

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to:
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part explaining and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.


This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Informative ballot (the ballot version may include conformance resources and examples; for exemplification purposes) [May 2021]
Connect-a-thon [May 2021]
Comment reconciliation [May-Ago 2021]
Publication as Informative IG [Sept 2021]
Connect-a-thon [Sept 2021]
STU ballot [Jan 2022]
Publication as STU IG (2 years) [Apr 2022]
Normative ballot [May 2024]
Publication as Normative IG [Sept 2024]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

Informative, STU to Normative

5d. Joint Copyright

No

6a. External Project Collaboration

RDA

6b. Content Already Developed

0%

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

12

Modifier

Giorgio Cangioli

Modify Date

Sep 22, 2020 12:40

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG 2

FHIR Infrastructure

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts

2g. Publishing Facilitator

Giorgio Cangioli

2i. Domain Expert Representative

Oya Beyan (Fraunhofer, RDA DE; EOSC FAIR WG); Carlos Luis Parra Calderón (EOSC; FAIR4Health coordinator; Andalusian Health); Catherine Chronaki (HL7 Europe); ALICIA MARTINEZ GARCIA (Andalusian Health Service); Anthony Juehne (RDA Reproducible Health Services WG ); Matthias Löbe (IMISE Leipzig)

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to:
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part explaining and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.


This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Informative ballot (the ballot version may include conformance resources and examples; for exemplification purposes) [May 2021]
Connect-a-thon [May 2021]
Comment reconciliation [May-Ago 2021]
Publication as Informative IG [Sept 2021]
Connect-a-thon [Sept 2021]
STU ballot [Jan 2022]
Publication as STU IG (2 years) [Apr 2022]
Normative ballot [May 2024]
Publication as Normative IG [Sept 2024]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

Informative, STU to Normative

5d. Joint Copyright

No

6a. External Project Collaboration

RDA

6b. Content Already Developed

0%

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

11

Modifier

Giorgio Cangioli

Modify Date

Sep 22, 2020 12:39

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG 2

FHIR Infrastructure

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts

2g. Publishing Facilitator

Giorgio Cangioli

2i. Domain Expert Representative

Oya Beyan (Fraunhofer, RDA DE; EOSC FAIR WG); Carlos Luis Parra Calderón (EOSC; FAIR4Health coordinator; Andalusian Health); Catherine Chronaki (HL7 Europe); ALICIA MARTINEZ GARCIA (Andalusian Health Service); Anthony Juehne (RDA and Reproducible Health Services WG Adoption Manager); Matthias Löbe (FAIR4Helath project, IMISE Leipzig)

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to:
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part explaining and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.


This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Informative ballot (the ballot version may include conformance resources and examples; for exemplification purposes) [May 2021]
Connect-a-thon [May 2021]
Comment reconciliation [May-Ago 2021]
Publication as Informative IG [Sept 2021]
Connect-a-thon [Sept 2021]
STU ballot [Jan 2022]
Publication as STU IG (2 years) [Apr 2022]
Normative ballot [May 2024]
Publication as Normative IG [Sept 2024]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

Informative, STU to Normative

5d. Joint Copyright

No

6a. External Project Collaboration

RDA

6b. Content Already Developed

0%

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

10

Modifier

Giorgio Cangioli

Modify Date

Sep 22, 2020 12:30

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG 2

FHIR Infrastructure

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts

2g. Publishing Facilitator

Giorgio Cangioli

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to:
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part explaining and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.


This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Informative ballot (the ballot version may include conformance resources and examples; for exemplification purposes) [May 2021]
Connect-a-thon [May 2021]
Comment reconciliation [May-Ago 2021]
Publication as Informative IG [Sept 2021]
Connect-a-thon [Sept 2021]
STU ballot [Jan 2022]
Publication as STU IG (2 years) [Apr 2022]
Normative ballot [May 2024]
Publication as Normative IG [Sept 2024]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

Informative, STU to Normative

5d. Joint Copyright

No

6a. External Project Collaboration

RDA

6b. Content Already Developed

0%

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

9

Modifier

Giorgio Cangioli

Modify Date

Sep 22, 2020 12:28

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG 2

FHIR Infrastructure

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts

2g. Publishing Facilitator

Giorgio Cangioli

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

(to be confirmed)
1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to:
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part explaining and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.


This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Informative ballot (the ballot version may include conformance resources and examples; for exemplification purposes) [May 2021]
Connect-a-thon [May 2021]
Comment reconciliation [May-Ago 2021]
Publication as Informative IG [Sept 2021]
Connect-a-thon [Sept 2021]
STU ballot [Jan 2022]
Publication as STU IG (2 years) [Apr 2022]
Normative ballot [May 2024]
Publication as Normative IG [Sept 2024]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

Informative, STU to Normative

5d. Joint Copyright

No

6a. External Project Collaboration

RDA

6b. Content Already Developed

0%

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

8

Modifier

Giorgio Cangioli

Modify Date

Sep 13, 2020 19:49

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG

Architecture Review Board

2b. Co-Sponsor WG 2

FHIR Infrastructure

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts

2g. Publishing Facilitator

Giorgio Cangioli

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

(to be confirmed)
1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to:
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part explaining and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.


This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Informative ballot (the ballot version may include conformance resources and examples; for exemplification purposes) [May 2021]
Connect-a-thon [May 2021]
Comment reconciliation [May-Ago 2021]
Publication as Informative IG [Sept 2021]
Connect-a-thon [Sept 2021]
STU ballot [Jan 2022]
Publication as STU IG (2 years) [Apr 2022]
Normative ballot [May 2024]
Publication as Normative IG [Sept 2024]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

Informative, STU to Normative

5d. Joint Copyright

No

6a. External Project Collaboration

RDA

6b. Content Already Developed

0%

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

7

Modifier

Giorgio Cangioli

Modify Date

Sep 13, 2020 08:43

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG

Architecture Review Board

2b. Co-Sponsor WG 2

FHIR Infrastructure

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts

2g. Publishing Facilitator

Giorgio Cangioli

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

(to be confirmed)
1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to:
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part explaining and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.


This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Informative ballot (the ballot version may include conformance resources and examples; for exemplification purposes) [May 2021]
Comment reconciliation
Publication as Informative IG [Sept 2021]
STU ballot [Jan 2022]
Publication as STU IG (2 years) [Apr 2022]
Normative ballot [May 2024]
Publication as Normative IG [Sept 2024]

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

Comment (aka Comment-Only), Informative, STU to Normative

6a. External Project Collaboration

RDA

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

6

Modifier

Giorgio Cangioli

Modify Date

Sep 12, 2020 13:00

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG

Architecture Review Board

2b. Co-Sponsor WG 2

FHIR Infrastructure

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts

2g. Publishing Facilitator

Giorgio Cangioli

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

(to be confirmed)
1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to:
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part explaining and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.


This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

Informative ballot (the ballot version may include conformance resources and examples; for exemplification purposes) [May 2021]
Comment reconciliation
Publication as Informative IG [Sept 2021]
STU ballot [Jan 2022]
STU publication (2 years) [
6) Normative ballot

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

Comment (aka Comment-Only), Informative, STU to Normative

6a. External Project Collaboration

RDA

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

5

Modifier

Dave Hamill

Modify Date

Aug 21, 2020 20:38

1a. Project Name

FAIRness for FHIR

1b. Project ID

1651

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG

Architecture Review Board

2b. Co-Sponsor WG 2

FHIR Infrastructure

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts

2g. Publishing Facilitator

Giorgio Cangioli

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

(to be confirmed)
1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to:
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part explaining and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.


This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

1) Public comment of the general introduction
2) Informative ballot (the ballot version may include conformance resources and examples; for exemplification purposes)
3) Comment reconciliation
4) Publication as Informative IG
5) STU ballot
6) STU publication (2 years)
6) Normative ballot

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

Comment (aka Comment-Only), Informative, STU to Normative

6a. External Project Collaboration

RDA

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

4

Modifier

Giorgio Cangioli

Modify Date

Aug 19, 2020 11:07

1a. Project Name

FAIRness for FHIR

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG

Architecture Review Board

2b. Co-Sponsor WG 2

FHIR Infrastructure

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts

2g. Publishing Facilitator

Giorgio Cangioli

2k. Conformance Facilitator

Giorgio Cangioli

2m. Implementers

(to be confirmed)
1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to:
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part explaining and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.


This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3c. Security Risk

Unknown

3e. Objectives/Deliverables and Target Dates

1) Public comment of the general introduction
2) Informative ballot (the ballot version may include conformance resources and examples; for exemplification purposes)
3) Comment reconciliation
4) Publication as Informative IG
5) STU ballot
6) STU publication (2 years)
6) Normative ballot

3f. Common Names / Keywords / Aliases:

FHIR4FAIR; FAIR;

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

3m. External Vocabularies

Unknown

4a. Products

FHIR Implementation Guide

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4.0.1

5a. Project Intent

Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Specify external organization

RDA

5b. Project Ballot Type

Comment (aka Comment-Only), Informative, STU to Normative

6a. External Project Collaboration

RDA

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

3

Modifier

Giorgio Cangioli

Modify Date

Aug 19, 2020 10:56

1a. Project Name

FAIRness for FHIR

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

Structured Documents

2b. Co-Sponsor WG

Architecture Review Board

2b. Co-Sponsor WG 2

FHIR Infrastructure

2d. Project Facilitator

Giorgio Cangioli

2e. Other Interested Parties (and roles)

BR&R would like to be kept informed of progress, particularly to ensure the relevance of FAIR principles in Clinical Research are taken account of.
CDS wishes to be an Interested Party, given that we are interested in applying the same FAIR principles to the creation, management, and access of knowledge artifacts

2g. Publishing Facilitator

Giorgio Cangioli

2m. Implementers

(to be confirmed)
1) FAIR4Health Project
2) SRDC
3) ATOS

3a. Project Scope

Develop a FHIR4FAIR FHIR Implementation Guide aiming to:
1) Identify how HL7 FHIR standard fulfills data FAIRness maturity indicators
a) analyse relationship between FAIR data object conceptual components (e.g. data, metadata, provenance, identifiers) and HL7 FHIR resources
b) analyze how RDA FAIR Maturity indicators are supported by specific HL7 FHIR resources
c) analyze how RDA Reproducible Health Data Services recommendations can be supported by HL7 FHIR
d) identify a minimum set of metadata to be fulfilled for specific sets of RDA FAIRness maturity indicators extended of health-related research data sets.
e) provide examples of best practices from EOSC (European Open Science Cloud https://www.eosc-portal.eu/) or NIH (https://www.nih.gov/)

2) Suggest an assessment methodology/checklist, exploring machine readable and manual assessment methods.

This guide should contain a large informative part explaining and a set of FHIR conformance resources and examples that provide, for selected case(s), a practical example of how FAIRness can be realized and assessed by using HL7 FHIR.


This project is intended to be the result of an active collaboration between RDA and HL7, the plan is to consult the Health care communities to comment and endorse the resulting HL7 FHIR IG taking into account relevant RDA group input.

3b. Project Need

Provide guidance on supporting FAIRness by using HL7 and specifically:
- the FAIR (Findability, Accessibility, Interoperability and Reusability) principles
- the proposed RDA (Research Data Alliance) - https://www.rd-alliance.org/ -recommendations on FAIR data maturity model, providing indicators for assessing adherence to the FAIR principles.
- the recommendations of RDA Reproducible Health Services Working Group for describing, documenting, and sharing metadata for health data curation workflows

3j. Backwards Compatibility

No

6i. Realm

Universal

Version

2

Modifier

Giorgio Cangioli

Modify Date

Jun 22, 2020 11:42

1a. Project Name

RDA Reproducible Health Data Services

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

Yes

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2d. Project Facilitator

Giorgio Cangioli

3a. Project Scope

Investigate possible projects and initiatives to be proposed within HL7 to promote and facilitate data FAIRness by using HL7 standards.
This action will be made in cooperation with the Reasearch Data Alliance (https://www.rd-alliance.org/).

3e. Objectives/Deliverables and Target Dates

Sept 2020 - PSS submitted

3j. Backwards Compatibility

No

6i. Realm

Universal

Version

1

Modifier

Giorgio Cangioli

Modify Date

Jun 22, 2020 09:29

1a. Project Name

RDA Reproducible Health Data Services

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

Yes

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2d. Project Facilitator

Giorgio Cangioli

3a. Project Scope

Investigate possible projects and initiatives to be proposed within HL7 to promote and facilitate data FAIRness by using HL7 standards.
This action will be made in cooperation with the Reasearch Data Alliance (https://www.rd-alliance.org/).

3j. Backwards Compatibility

No

6i. Realm

Universal