https://github.com/jmandel/sample_ccdas

Repository of Sample CCDA Documents -- all comers welcome!
https://github.com/jmandel/sample_ccdas

Last synced: 19 days ago
JSON representation

Repository of Sample CCDA Documents -- all comers welcome!

• Host: GitHub
• URL: https://github.com/jmandel/sample_ccdas
• Owner: jmandel
• Created: 2012-07-20T18:24:20.000Z (over 12 years ago)
• Default Branch: master
• Last Pushed: 2018-07-17T18:19:46.000Z (over 6 years ago)
• Last Synced: 2024-10-06T15:42:09.580Z (about 1 month ago)
• Language: HTML
• Size: 5.84 MB
• Stars: 117
• Watchers: 32
• Forks: 389
• Open Issues: 2
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Share Your C-CDA with the SMART Community

* By copy/paste: http://bit.ly/contribute-ccda  *or*

* By forking this repository and sumitting a pull request

# Sample CCDA Documents

### (Consolidated Clinical Document Architecture)

### What

This is a repository to collect **Sample CCDA Documents**. (No protected health information.) These samples are available under the [Creative Commons Attribution 4.0 license](https://creativecommons.org/licenses/by/4.0/).

### Why?

*Lots* of people will be implementing CCDA very soon; many have already started.

But there are big questions about how to do what, and while an excellent 

implementation guide is a must, examples matter too.  The community would

benefit immensely from a public collection of examples that can be:

 * dissected,

 * discussed, and 

 * corrected over time.

The goals are to provide:

 * examples for the developer community 

 * a platform to identify and correct implementation errors

 * a public arena to identify areas of ambiguity and variability

### Why not?

If there are barriers (organizational, technical, cultural, or otherwise),

can we break them down? [Discuss](https://github.com/chb/sample_ccdas/issues).

### How?

*All comers welcome*! To contribute samples, just:

 1.  Fork this repository to your GitHub account

 2.  Add an example file

 3.  Issue a GitHub "Pull request"

... or just share by e-mail with `joshua dot mandel at childrens.harvard.edu`

### Fine print

Sample documents should be available under an open license and should not 

involve PHI.  Ideally these documents would represent actual output of 

real export pipelines.