[ 
https://issues.apache.org/jira/browse/NIFI-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837801#comment-15837801
 ] 

ASF GitHub Bot commented on NIFI-3147:
--------------------------------------

Github user kedarchitale commented on the issue:

    https://github.com/apache/nifi/pull/1312
  
    @jfrazee The consideration of separate bundle was based on SOLID principle. 
The HL7 bundle address HL7 V2 which is ascii/text protocol with XML support 
where as CDA is completely XML based. HL7 V3 is based on RIM model and CDA is 
one specific domain of V3 for clinical documents. The adoption of HL7 V3 varies 
as compared to legacy HL7 V2. The underlying parsers are different (HAPI and 
MDHT). CDA bundle is based on mapping, which will grow as more sections/entries 
are mapped by contributors. For now, keeping them as separate bundles makes 
sense, as they can be used/maintained separately without impacting each other.
    
    Regarding the XML file, this is used for unit testing only and not shipped 
with the bundle runtime deployment. This is a Cerner Sample that was shared 
over github by @jmandel and not clear about the exact origins of this file. The 
markdown for that repository states that sample documents should be available 
under an open license, and ASLv2 being would be such an open license.


> Build processor to parse CCDA into attributes and JSON
> ------------------------------------------------------
>
>                 Key: NIFI-3147
>                 URL: https://issues.apache.org/jira/browse/NIFI-3147
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Kedar Chitale
>              Labels: attributes, ccda, healthcare, json, parser
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Accept a CCDA document, Parse the document to create JSON text and individual 
> attributes for example code.codeSystemName=LOINC



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to