This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR"
Jump to navigation
Jump to search
| Line 95: | Line 95: | ||
** [[FHIR Methodology Process]] - how the methodology is developed and maintained | ** [[FHIR Methodology Process]] - how the methodology is developed and maintained | ||
** [[FHIR Repository Process]] - Repository governance process and requirements | ** [[FHIR Repository Process]] - Repository governance process and requirements | ||
| − | ** [[http://wiki.hl7.org/images/a/a2/HL7_International_Repository_Governance_Process_and_Requirements_August_2017_V4.02.zip FHIR Registry Requirements and Gap Assessment | + | ** [[http://wiki.hl7.org/images/a/a2/HL7_International_Repository_Governance_Process_and_Requirements_August_2017_V4.02.zip FHIR Registry Requirements and Gap Assessment] |
| − | ** | + | *** [FHIR Guide to Designing Resources|Methodology Guidelines]] - Content and quality guidelines |
** [[FHIR Design Patterns|Design Patterns]] | ** [[FHIR Design Patterns|Design Patterns]] | ||
** [[FHIR Comparison to other RESTful API specifications]] | ** [[FHIR Comparison to other RESTful API specifications]] | ||
Revision as of 15:49, 16 January 2018
Fast Healthcare Interoperability Resources (FHIR, pronounced "Fire") defines a set of "Resources" that represent granular clinical concepts. The resources can be managed in isolation, or aggregated into complex documents. Technically, FHIR is designed for the web; the resources are based on simple XML or JSON structures, with an http-based RESTful protocol where each resource has predictable URL. Where possible, open internet standards are used for data representation.
Community Participation Rules: FHIR Code of Conduct, FHIR Intellectual Property Rules
| FHIR Implementation | FHIR Development | Organizational |
|
|
|
