-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CCD Export: Validation still failing #51
Comments
OK, what's missing is the lab set name. I'm pulling that from the summary field of the lab order section, which must be missing from the JSON you're exporting from. Can you populate the summary field and try again? |
It is non-trivial to associate a lab order right.. will probably take me 30 mins or so to try to fake it. It's also weird that we would need to have a lab name from the lab order because nothing else has used lab orders with lab results up to this point. Can you use the name field from the lab results if there's no summary field in the lab order? |
Well there's a fundamental issue there. The structure of labs is like this: There's a set of labs, with an order (optional) and results. Within the results are individual tests. This is how the JSON is structured basically. Now I have a whole slew of concerns for after certification. For example, I believe each test should/could have its own LOINC code, in addition to the battery of tests (set of labs) having one as well. But that's not an issue that's being brought up so I'm just going to save it all for later. However, one of them has been twisting my brain for awhile now. I have a LOINC code in the labResult object, but no corresponding descriptor. This has been pretty troublesome, because whenever I have to export a LOINC code, I almost always have to include a corresponding descriptor that is never right next to it. But it was possible to work around that case. When I'm looping through each individual test in the labTestResult objects, I'm just pulling the LOINC code from the parent labResult object. It's a little messy/redundant, but we're getting by. Each test has exactly one LOINC code in the parent object they all share. It's a many-to-one relationship. However, in this case here, it's not as simple. The only english descriptor for any result is in the object for the individual test, buried two levels deep. And there can be more than one of them, with different names. So when I have to give a set of labs a name, I have my one single LOINC code, but no single description. The only thing I could go on was the order summary. TL;DR: In the JSON, I need one field for each lab (as in the set of labs, as opposed to each individual lab test) that can provide me with a description. It doesn't need to be the order summary necessarily, but there has to be exactly one for each item in the JSON's lab array. |
Another way I could have put it would have been to ask how possible it'd be to add a description/summary on the same level in the hierarchy as the loincCode... with that, I wouldn't need to look at the order object. |
What did we use for this previously? I know this was passing yesterday On Thu, Apr 4, 2013 at 7:49 PM, Skwerl notifications@github.com wrote:
|
odd, i've always been using order summary. |
Adding a field to the API will also require a new app build. Any issue On Thursday, April 4, 2013, Skwerl wrote:
|
More than one result = more than one name. Which do I use? |
Touché.. Can you take the first one? The field doesn't show up on the human readable so I'm not super concerned as long as it validates On Thu, Apr 4, 2013 at 8:27 PM, Skwerl notifications@github.com wrote:
|
gnarly hack, but can do. if that's the best option. at least i can make it the last resort if there's no order summary. |
Agreed.. Does it pass validation? On Thu, Apr 4, 2013 at 8:42 PM, Skwerl notifications@github.com wrote:
|
Yeah, CCD export passes with my JSON, now even when I remove lab order summary. Give it a shot. |
The CCD export below is still failing validation. There are three labs associated to the patient and all three labs have type set.
The text was updated successfully, but these errors were encountered: