Difference between revisions of "Clinical Document Architecture"

From HL7Wiki
Jump to navigation Jump to search
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]
 +
 +
* CDA Implementation Guides
 +
** [http://www.hl7.org/implement/standards/product_brief.cfm?product_id=408 Consolidated CDA (C-CDA)]
 +
** [http://www.hl7.org/implement/standards/product_brief.cfm?product_id=447 C-CDA Companion Guide]
  
 
*Testing
 
*Testing
Line 32: Line 36:
 
**[https://sitenv.org/scorecard/ C-CDA Scorecard]
 
**[https://sitenv.org/scorecard/ C-CDA Scorecard]
  
* CDA Implementations?
+
 
 
* Transformation page?
 
* Transformation page?
  

Revision as of 15:43, 5 January 2018

Temporary FHIR logo

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


  • Transformation page?