This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Clinical Document Architecture"
Jump to navigation
Jump to search
Bamarquard (talk | contribs) |
Bamarquard (talk | contribs) |
||
Line 35: | Line 35: | ||
**[https://sitenv.org/sandbox-ccda/ccda-validator C-CDA Validator] | **[https://sitenv.org/sandbox-ccda/ccda-validator C-CDA Validator] | ||
**[https://sitenv.org/scorecard/ C-CDA Scorecard] | **[https://sitenv.org/scorecard/ C-CDA Scorecard] | ||
− | |||
− | |||
− | |||
*Implementation-a-thons | *Implementation-a-thons | ||
**[http://wiki.hl7.org/index.php?title=C-CDA:_Enhancing_Implementation_(ONC_Grant_Project) C-CDA Implementation-a-thons] | **[http://wiki.hl7.org/index.php?title=C-CDA:_Enhancing_Implementation_(ONC_Grant_Project) C-CDA Implementation-a-thons] | ||
− | + | ||
− | |||
|valign=top| | |valign=top| |
Revision as of 15:46, 5 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
CDA Implementation | CDA Standards Development | Organizational |
|
|
|