Thanks for the link. Now we're getting somewhere...

It looks like this is a bit of a difference in modeling between C-CDA and C32. Let me summarize:

In C-CDA, there is a `Procedures Section` and a `Results Section`. 

 * Procedures would be, for example, surgeries you've had.  They're fundamentally defined by a procedure code (indicating *what happened*).  

 * Results, on the other hand, are fundamentally defined not just by a code (e.g. the LOINC code for White Blood Cell Count) but also a **value** (e.g. 4500/uL).

In C32 v2.5, there is also a `Procedures Section`  (well, `Surgeries` anyway) that contains a [list of surgeries](http://cdatools.org/infocenter/index.jsp?topic=%2Forg.openhealthtools.mdht.uml.cda.hitsp.flat.doc%2Fclasses%2FSurgeriesSection.html), etc., as well as a `Results` section:

 * Procedures here are basically surgeries...

 * Results Section includes Result entries (which have a code + value, as in C-CDA), *as well as* Procedure entries, which are supposed to indicate the procedure during/by which the results were observed.  

What does all this mean, if we're trying to normalize data?  At a first pass we should say:

C-CDA or C32, no matter -- the JSON structure will have a list of Procedures and a list of Results (which we shouldn't call "labs" because it's more than just labs...)  To populate it, we'd take the Procedure entries from a Procedure section, and the Result Entries from a Results section.

Remaining question is what to do with C32's extra Procedure entries that appear in the Results section? I'm not sure how useful they are, generally, and I'm really not sure how individual result entries are supposed to map back to the Procedure entries they "come from."  Perhaps the simplest thing to do, for now, is simply add them to the JSON Procedures list.

Does any of that make sense?