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 27: | Line 27: | ||
** [http://www.hl7.org/events/workgroupmeetings.cfm?ref=nav Come to Working Group!] | ** [http://www.hl7.org/events/workgroupmeetings.cfm?ref=nav Come to Working Group!] | ||
** [http://cdasearch.hl7.org/ CDA Examples] | ** [http://cdasearch.hl7.org/ CDA Examples] | ||
− | |||
− | |||
− | |||
*Testing | *Testing | ||
− | * | + | **[https://sitenv.org/sandbox-ccda/ccda-validator C-CDA Validator] |
+ | **[https://sitenv.org/scorecard/ C-CDA Scorecard] | ||
* CDA Implementations? | * CDA Implementations? |
Revision as of 15:38, 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 |
|
|
|