Stream: cda to fhir
Topic: Code differences in FHIR and CDA
Jon Price (Aug 16 2016 at 03:42):
Has anyone run into the problem with a code been defined slightly differently between FHIR and CDA, i.e. in HL7 v3 its valid xs:token with no internal whitespace and in FHIR its no whitespace other than single spaces in the contents.
ref for FHIR http://hl7.org/fhir/datatypes.html#code
ref for V3 https://www.hl7.org/documentcenter/public_temp_AE2A570C-1C23-BA17-0C3700E453DF1C0B/wg/inm/datatypes-its-xml20050714.htm#dtimpl-CS
Jon Price (Aug 16 2016 at 03:42):
I guess its not a problem when going from CDA to FHIR, but not sure how to handle FHIR to CDA.
Grahame Grieve (Aug 16 2016 at 05:11):
there's a few data types that are more permissive in FHIR than CDA. That's one minor difference that actually comes from the v3 process, not FHIR. You shouldn't ever encounter content that could be transformed to CDA that has spaces in the codes.
Jon Price (Aug 17 2016 at 22:17):
Can you explain more what you mean by " You shouldn't ever encounter content that could be transformed to CDA that has spaces in the codes". The problem I think I could get in the FHIR to CDA transform is when there is a local code in the FHIR content where spaces in codes are valid, to transform this into CDA where spaces are not allowed in codes.
Grahame Grieve (Aug 17 2016 at 23:18):
why would you encounter a code with a space in it? It's not something done by any of the code systems that I know of that are relevant for content that could be in CDA
Grahame Grieve (Aug 17 2016 at 23:18):
I guess you could if it's a local code, but if they're doing that, they'll have to fix them?
Jayashree Surnar (Mar 27 2017 at 05:10):
hello every One, can anybody suggest which one is better to create the documents CCDA or Fhir doucument?
Lloyd McKenzie (Mar 27 2017 at 13:41):
If you need documents to be consumed by systems that use CCDA, then use that. If not, then FHIR documents will probably be easier to work with.
John Moehrke (Mar 27 2017 at 18:20):
CDA is a normative standard. FHIR is not yet normative, it is a "Standard for Trial Use"....
Lloyd McKenzie (Mar 27 2017 at 19:16):
CCDA and FHIR are both "Standard for Trial Use"
Lloyd McKenzie (Mar 27 2017 at 19:16):
But yes, the underlying CDA standard is normative
Jayashree Surnar (Jun 02 2017 at 04:24):
hello all, is there any documentation for Converting the fhir documents to other formates like ccda,pdf etc. and viceversa.
Jayashree Surnar (Jun 02 2017 at 04:29):
in fhir by using Composition resource we are creating the documentation.like that on what basis we create C-CDAs is there any documentation for that?
Lloyd McKenzie (Jun 02 2017 at 04:51):
Have you looked at the CCDA on FHIR spec? http://hl7.org/fhir/us/ccda/index.html
Lloyd McKenzie (Jun 02 2017 at 04:52):
In terms of converting to PDF, one possibility would be converting a resource's narrative to PDF - there are certainly tools available that could handle XHTML -> PDF conversion. Though you'd have to verify that the narrative met your needs.
Jayashree Surnar (Jun 02 2017 at 05:20):
and in HL7 they created some profiles CCDA on FHIR based on daf profiles. so here my doubt is if i want to create a document for pfisical & history in that case shall i use C-CDA on FHIR History and Physical profile or need to create our own profile? because it's based on us-core right, in our cas the referenced resources(ex: patient profile) may be diff.
Jayashree Surnar (Jun 02 2017 at 05:25):
yes @Lloyd McKenzie Mckenzie, fewdays i have gone through that doc. but dnt know which tool they have used to create that andif i want to add some more sections then how can i do that?
is there any tools available to convert fhir document to ccda or other formates and viceversa?
Lloyd McKenzie (Jun 02 2017 at 13:35):
You don't necessarily need to use documents to capture physical & history data at all. Some jurisdictions have done work on creating customized versions of CCDA for use within their boundaries, but I don't think any of that work has come to the FHIR space yet. You'd certainly need to create your own profiles. I know work has happened on automated conversion, but I don't know how far along that work is or what caveats need to hold in order for automated conversion to work.
Gary Teichrow (Jun 02 2017 at 17:39):
@Jayashree Surnar , you might want to check this project out: https://github.com/synthetichealth/synthea
It's possible that in looking how they generate 'synthetic' C-CDA as well as FHIR models you might see a path to do what you are looking to do. FWIW, I've found this project very useful for generating 'fake' but 'realistic' data for tinkering. Cheers.
Jayashree Surnar (Jun 06 2017 at 04:28):
hello all, we are using HAPI-FHIR server. to create the documents in fhir we are using composition resource. in fhir documentation page they given we can use Composition and Bundle resources to create the documents. i understood the composition resource.
but not clear with Bundle resource.
is to the composition resource we need to add sections,entries along with the meta data. after that do we need to add that Composition to Bundle resource as entry? or no need?
if i'm not adding composition to Bundle then how it will going to store in the server(as Composition resource or Bundle)
what's the relationship b/w Composition and Bundle?
*and if we get ccdas or pdfs etc(other than fhir docs)from outside (other systems) then who is going to take care of convertion(other formates to fhir doc)?*
Lloyd McKenzie (Jun 06 2017 at 04:41):
A FHIR document is a Bundle resource that starts with a Composition resource. The Bundle will also contain things like the Patient and all of the relevant resources to represent the content of the document (Observation, Condition, Encounter, AllergyIntolerance, etc.)
Jayashree Surnar (Jun 06 2017 at 04:46):
okay, but as part of sections in composition there is an entry.if we add the resources releted to that sections there. again whats the use of adding the resources in bundle entry?
Jayashree Surnar (Jun 06 2017 at 04:47):
i'm confusing whats the main purpose of sections, entries as part of composition and entries in bundle resource.
Lloyd McKenzie (Jun 06 2017 at 04:54):
The entries don't contain resources, just point to them.
Jayashree Surnar (Jun 06 2017 at 05:09):
where? in bundle or composition?
Lloyd McKenzie (Jun 06 2017 at 05:10):
Composition.section.entry contains references to resources that must appear in the Bundle
Lloyd McKenzie (Jun 06 2017 at 05:12):
There's an example of a document listed in the examples section under Composition: http://hl7.org/fhir/document-example-dischargesummary.html
Jayashree Surnar (Jun 06 2017 at 05:12):
ohh. means what are the entries we specified in the composition's entries, that should be added in bundle's entry. right
Lloyd McKenzie (Jun 06 2017 at 05:12):
Look at the JSON or XML
Jayashree Surnar (Jun 06 2017 at 05:12):
okay. thank you somuch
Jayashree Surnar (Jun 08 2017 at 05:42):
i'm trying to create our CCDA on Fir for History and physical by using forge tool but while saving as snapshot it's getting struck,actually it's forge tool bug. if use clinfhir, i didn't fined the consept of slicing there.
so i don't know how to continue my work. any help please.
Thank you.
Michel Rutten (Jun 12 2017 at 08:27):
Hi @Jayashree Surnar, we're working on a minor update that will hopefully also include a fix for this issue. In the mean time, you may be able to work around this by moving/saving your profile to a clean output folder.
Jayashree Surnar (Jun 13 2017 at 06:36):
tnq @Michel Rutten
Last updated: Apr 12 2022 at 19:14 UTC
