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 18: | Line 18: | ||
** [http://www.hl7.org/special/committees/cdamg/leadership.cfm CDA Management Group Leadership] | ** [http://www.hl7.org/special/committees/cdamg/leadership.cfm CDA Management Group Leadership] | ||
** [http://www.hl7.org/Special/committees/structure/leadership.cfm Structured Documents WG Leadership] | ** [http://www.hl7.org/Special/committees/structure/leadership.cfm Structured Documents WG Leadership] | ||
− | ** [http://www.hl7.org/myhl7/managelistservs.cfm?ref=nav Select Structured Documents | + | ** [http://www.hl7.org/myhl7/managelistservs.cfm?ref=nav HL7 listservs] |
+ | *** Select Structured Documents > Primary List for Structured Documents | ||
+ | *** Select Structured Documents > Continuity of Care Document | ||
* Help / Getting Started | * Help / Getting Started |
Revision as of 15:26, 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 |
|
|
|