├── Allscripts Samples
├── Enterprise EHR
│ └── readme.txt
├── Professional EHR
│ └── readme.txt
├── Sunrise Clinical Manager
│ └── readme.txt
└── Internal Test with MU 2 data
│ └── readme.txt
├── Kinsights Samples
└── README.md
├── README.md
├── mTuitive OpNote Samples
├── README.md
├── colonoscopy.xml
├── hernia.xml
├── cataract.xml
├── breast surgery.xml
└── knee.xml
├── HL7 Samples
├── UD.sample.xml
└── DIR.sample.xml
└── Kareo Samples
└── Kareo_CCD_export_Joey_Miller.ccd
/Allscripts Samples/Enterprise EHR/readme.txt:
--------------------------------------------------------------------------------
1 | The files in this folder came from an Allscripts EHR product.
--------------------------------------------------------------------------------
/Allscripts Samples/Professional EHR/readme.txt:
--------------------------------------------------------------------------------
1 | The files in this folder came from an Allscripts EHR product.
--------------------------------------------------------------------------------
/Allscripts Samples/Sunrise Clinical Manager/readme.txt:
--------------------------------------------------------------------------------
1 | The files in this folder came from an Allscripts EHR product.
--------------------------------------------------------------------------------
/Allscripts Samples/Internal Test with MU 2 data/readme.txt:
--------------------------------------------------------------------------------
1 | The files in this folder came from an internal testing tool generating documents using MU 2 test data.
--------------------------------------------------------------------------------
/Kinsights Samples/README.md:
--------------------------------------------------------------------------------
1 | # Kinsights C-CDA Sample
2 |
3 | Kinsights allows its users to export their records via a [bbClear](https://blue-button.github.io/bbClear/) HTML document, which contains the raw data in the form of an embedded C-CDA XML document.
4 |
5 | The basic structure of the bbClear document is:
6 |
7 |
8 |
...
9 | ...
10 |
11 |
14 |
15 | The XML data is extractable by the end user in-browser, and this XML file is included in this directory as well.
16 |
17 | We hope other C-CDA parsers will eventually recognize the more patient-friendly bbClear wrapper and allow it as an acceptable format for C-CDA importing when the end-user is offered the option to upload C-CDA data.
18 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # Share Your C-CDA with the SMART Community
2 | * By copy/paste: http://bit.ly/contribute-ccda *or*
3 | * By forking this repository and sumitting a pull request
4 |
5 | # Sample CCDA Documents
6 | ### (Consolidated Clinical Document Architecture)
7 |
8 | ### What
9 | 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/).
10 |
11 | ### Why?
12 | *Lots* of people will be implementing CCDA very soon; many have already started.
13 | But there are big questions about how to do what, and while an excellent
14 | implementation guide is a must, examples matter too. The community would
15 | benefit immensely from a public collection of examples that can be:
16 | * dissected,
17 | * discussed, and
18 | * corrected over time.
19 |
20 | The goals are to provide:
21 | * examples for the developer community
22 | * a platform to identify and correct implementation errors
23 | * a public arena to identify areas of ambiguity and variability
24 |
25 | ### Why not?
26 | If there are barriers (organizational, technical, cultural, or otherwise),
27 | can we break them down? [Discuss](https://github.com/chb/sample_ccdas/issues).
28 |
29 | ### How?
30 | *All comers welcome*! To contribute samples, just:
31 | 1. Fork this repository to your GitHub account
32 | 2. Add an example file
33 | 3. Issue a GitHub "Pull request"
34 |
35 | ... or just share by e-mail with `joshua dot mandel at childrens.harvard.edu`
36 |
37 | ### Fine print
38 | Sample documents should be available under an open license and should not
39 | involve PHI. Ideally these documents would represent actual output of
40 | real export pipelines.
41 |
--------------------------------------------------------------------------------
/mTuitive OpNote Samples/README.md:
--------------------------------------------------------------------------------
1 | #mTuitive OpNote CCDA Samples
2 |
3 | These samples are intended to comply with the [Consolidated CDA Implementation Guide (IG)](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=258).
4 |
5 | [mTuitive OpNote](http://mtuitive.com/opnote) is a web-based application that lets surgeons easily create
6 | structured operative reports instead of narrative dictation. This data is useful for research, clinical automation,
7 | billing, etc.
8 |
9 | CCDA is intended to provide some guidance about structured various clinical documents and is already very useful
10 | for exchanging operative reports. The choice of open CDA templates proved very helpful, allowing us to include additional
11 | sections not covered by the IG and entries not specified by the IG.
12 |
13 | ##Areas for Improvement
14 | The current implementation by mTuitive is useful as-is, but there are several areas that could use additional refinement:
15 | * Encode diagnoses as ICD10 or SNOMED. Since ICD9 is used in production, that's what we've provided here.
16 | * More entry level section templates
17 | * H&P, Discharge Summary, and Procedure Note implementations
18 | * LOINC codes for all section templates
19 |
20 | ##Suggestions for CCDA 2.0
21 |
22 | The difference between operative note and procedure note is murky. We would be in favor of consolidating them into
23 | one template or providing applicable CPT codes for each.
24 |
25 | Real-world operative reports often document multiple procedures. The specification clearly only allows one instance of
26 | some important required sections, which makes this difficult. In mTuitive's production application, each procedure has
27 | its own instance of some fields.
28 |
29 | To implement this with CCDA, we include a serviceEvent for each procedure. Within the document body, we use a container
30 | section that corresponds to each serviceEvent being documented. Each container section includes a ProcedureContext
31 | template to set the context for sub-sections within its scope to the appropriate procedure. This works but is not
32 | strictly compliant because there may be multiple operative description or laterality fields in the document.
33 | We felt this was preferable to concatenating all of the relevant fields into one text block.
34 |
35 | For example:
36 |
37 |
38 | Operative Description
39 |
40 |
41 | Extracapsular cataract removal with insertion of intraocular lens prosthesis (1 stage procedure), manual or mechanical technique (eg, irrigation and aspiration or phacoemulsification) (66984)
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 | Laterality
53 |
54 |
55 | Bilateral
56 |
57 |
58 |
59 |
60 |
61 |
62 |
63 |
64 | Operation Description
65 |
66 |
67 | Lieberman lid speculum placed between eyelids
68 | Superior temporal incision performed in beveled three-stage maneuver
69 | ...
70 | ##Validation
71 |
72 | There are two known validation errors found using the [Lantana CCDA validator](https://www.lantanagroup.com/validator/connectathon.jsp).
73 | This tool was helpful for finding cda schema and ccda schematron violations with a single tool.
74 |
75 | 1. An unknown address is flagged as an error. When using , the validator still complains
76 | about missing child elements. [Others](https://www.projects.openhealthtools.org/sf/go/artf3450?returnUrlKey=1353511042478)
77 | seem to have experienced the same issue.
78 | >If country is US, this addr SHALL contain exactly one [1..1] state, which SHALL be selected from ValueSet 2.16.840.1.113883.3.88.12.80.1 StateValueSet DYNAMIC (CONF:5402).
79 | >Location: /ClinicalDocument[1]
80 | >Test: (cda:recordTarget/cda:patientRole/cda:addr[cda:country='US' or cda:country='USA']) and cda:recordTarget/cda:patientRole/cda:addr/cda:state
81 |
82 | 2. As noted above, multiple procedure descriptions are used and scoped to the appropriate serviceEvent using the
83 | Procedure Context template. The validator complains because there are multiple procedure description elements where
84 | only 1 is allowed. The schema will hopefully be relaxed in a future version to allow 1 or more procedure descriptions.
85 | >SHALL contain exactly one [1..1] Procedure Description Section (templateId:2.16.840.1.113883.10.20.22.2.27) (CONF:9896).
86 | >Location: /ClinicalDocument[1]
87 | >Test: count(//cda:section[cda:templateId/@root='2.16.840.1.113883.10.20.22.2.27'])=1
88 |
89 | The [SMART C-CDA Scorecard](http://ccda-scorecard.smartplatforms.org/) ranks each document at 72%. 100% of applicable best practices are met. The documents are
90 | scored lower for missing structured vitals, which we suspect is a mistake because our documents do not include vitals.
91 | This tool was particularly helpful in finding coding inconsitencies, such as mismatched LOINC display names.
92 |
93 |
94 |
95 |
--------------------------------------------------------------------------------
/HL7 Samples/UD.sample.xml:
--------------------------------------------------------------------------------
1 |
2 |
3 |
13 |
17 |
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 | Discharge Summary (UD)
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 | 17 Daws Rd.
50 | Blue Bell
51 | MA
52 | 02368
53 | US
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 | Mr.
62 | Adam
63 | Frankie
64 |
65 | Everyman
66 |
67 |
68 |
69 |
70 |
71 |
72 |
73 |
74 |
75 |
76 |
77 | 17 Daws Rd.
78 | Blue Bell
79 | MA
80 | 02368
81 | US
82 |
83 |
84 |
85 |
86 |
87 | Ralph
88 | Relative
89 |
90 |
91 |
92 |
93 |
94 |
95 | MA
96 | 02368
97 | USA
98 |
99 |
100 |
101 |
102 |
103 |
104 |
105 |
106 |
107 |
108 |
109 | Good Health Clinic
110 |
111 |
112 | 21 North Ave
113 | Burlington
114 | MA
115 | 02368
116 | USA
117 |
118 |
119 |
120 |
121 |
122 |
123 |
124 |
125 |
126 | 21 North Ave.
127 | Burlington
128 | MA
129 | 02368
130 | USA
131 |
132 |
133 |
134 |
135 | Henry
136 | Seven
137 |
138 |
139 |
140 |
141 |
142 |
143 |
144 |
145 | 21 North Ave.
146 | Burlington
147 | MA
148 | 02368
149 | USA
150 |
151 |
152 |
153 |
154 | Henry
155 | Seven
156 |
157 |
158 |
159 |
160 |
161 |
162 |
163 |
164 | 21 North Ave.
165 | Burlington
166 | MA
167 | 02368
168 | USA
169 |
170 |
171 |
172 |
173 | Henry
174 | Seven
175 |
176 |
177 |
178 |
179 |
180 |
181 |
182 |
183 |
184 |
185 | Rose
186 | Everyman
187 |
188 |
189 |
190 |
191 |
192 |
193 |
194 |
195 | Good Health Clinic
196 |
197 |
198 | 17 Daws Rd.
199 | Blue Bell
200 | MA
201 | 02368
202 | USA
203 |
204 |
205 |
206 |
207 |
208 |
209 |
210 |
211 | Henry
212 | Seven
213 |
214 |
215 |
216 | Good Health Clinic
217 |
218 |
219 |
220 |
221 |
222 |
223 |
224 |
225 |
226 | 21 North Ave.
227 | Burlington
228 | MA
229 | 02368
230 | USA
231 |
232 |
233 |
234 |
235 | Henry
236 | Seven
237 |
238 |
239 |
240 |
241 |
242 |
243 |
244 |
245 |
246 |
247 | 21 North Ave.
248 | Burlington
249 | MA
250 | 02368
251 | USA
252 |
253 |
254 |
255 |
256 | Henry
257 | Seven
258 |
259 |
260 |
261 |
262 |
269 |
270 |
271 |
272 |
273 |
274 |
275 |
276 |
277 |
278 |
287 |
288 |
--------------------------------------------------------------------------------
/Kareo Samples/Kareo_CCD_export_Joey_Miller.ccd:
--------------------------------------------------------------------------------
1 | 26 N. Martin StreetLos AngelesCA90005United States of AmericaJOEYnullMILLERKAREO EHRAllergies and Adverse Reactions
416 | The cardiomediastinum is within normal limits. The
417 | trachea is midline. The previously described opacity at the medial
418 | right lung base has cleared. There are no new infiltrates. There is
419 | a new round density at the left hilus, superiorly (diameter about
420 | 45mm). A CT scan is recommended for further evaluation. The pleural
421 | spaces are clear. The visualized musculoskeletal structures and the
422 | upper abdomen are stable and unremarkable.
423 |
424 |
425 |