Loading...

XML

Word

Printable

JSON

Specification:

US Making EHR Data More available for Research and Public Health (MedMorph) (FHIR)
Raised in Version:

0.1.0
Work Group:

Public Health
Related Page(s):

Use Cases
Related Section(s):
3.3
Grouping:
- Block-Vote-2
Resolution Description:

Hide

Federated vs Single database is an artifact of the deployment architecture. The APIs that need to be supported will still be defined at a Knowledge Artifact Repository level as a single actor. This could be implemented as a Federated Database if desired.

Show
Federated vs Single database is an artifact of the deployment architecture. The APIs that need to be supported will still be defined at a Knowledge Artifact Repository level as a single actor. This could be implemented as a Federated Database if desired.
Resolution Vote:
Becky Angeles / Genny Luensman : 31 - 0 - 4

May want to highlight some constructs of a federated database that metadata (e.g. transaction audits)

(Comment 14 - imported by: Jean Duteau)

is voted on by

BALLOT-15007 Affirmative - Kevin Geminiuc : 2021-Jan-FHIR IG MEDMORPH R1 STU