Github user jfrazee commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/1312#discussion_r102478735
  
    --- Diff: 
nifi-nar-bundles/nifi-ccda-bundle/nifi-ccda-processors/src/main/resources/docs/org.apache.nifi.processors.ccda.ExtractCCDAAttributes/additionalDetails.html
 ---
    @@ -0,0 +1,108 @@
    +<!DOCTYPE html>
    +<html lang="en">
    +    <!--
    +      Licensed to the Apache Software Foundation (ASF) under one or more
    +      contributor license agreements.  See the NOTICE file distributed with
    +      this work for additional information regarding copyright ownership.
    +      The ASF licenses this file to You under the Apache License, Version 
2.0
    +      (the "License"); you may not use this file except in compliance with
    +      the License.  You may obtain a copy of the License at
    +          http://www.apache.org/licenses/LICENSE-2.0
    +      Unless required by applicable law or agreed to in writing, software
    +      distributed under the License is distributed on an "AS IS" BASIS,
    +      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 
implied.
    +      See the License for the specific language governing permissions and
    +      limitations under the License.
    +    -->
    +    <head>
    +        <meta charset="utf-8" />
    +        <title>ExtractCCDAAttributes</title>
    +        <link rel="stylesheet" href="../../css/component-usage.css" 
type="text/css" />
    +    </head>
    +
    +    <body>
    +        <!-- Processor Documentation 
================================================== -->
    +        <h2>Apache NiFi CCDA Processor</h2>
    +        <p>
    +            CCDA Processor Bundle provides parser for Consolidated-CDA 
documents</br>
    +            This processor provides JSON in FlowFile content. Pretty 
Printing can be set as a property while configuring the processor.</br>
    +            Individual attributes are set as FlowFile attributes. The 
attributes are named as &lt;Parent&gt; &lt;dot&gt; &lt;Key&gt;.</br>
    +            If the Parent is repeating, the naming will be &lt;Parent&gt; 
&lt;underscore&gt; &lt;Parent Index&gt; &lt;dot&gt; &lt;Key&gt;.</br>
    +        </p>
    +        <h3>Example JSON Output</h3>
    +        <p>
    +            <pre><code>
    +    "observation": [
    +      {
    +        "id": [
    +          {
    +            "extension": "121387536",
    +            "root": "2.16.840.1.113883.1.13.99999.999239"
    +          }
    +        ],
    +        "values": {
    +          "code": "194828000",
    +          "codeSystem": "2.16.840.1.113883.6.96",
    +          "codeSystemName": "SNOMED CT",
    +          "displayName": "Angina (disorder)",
    +          "translations": [
    +            {
    +              "code": "413.9",
    +              "codeSystem": "2.16.840.1.113883.6.103",
    +              "codeSystemName": "ICD-9CM (diagnosis codes)",
    +              "displayName": "Other and unspecified angina pectoris"
    +            }
    +          ]
    +        },
    +        "statusCode": {
    +          "code": "completed"
    +        },
    +        "effectiveTime": {
    +          "low": "20130711"
    +        }
    +      }
    +    ]
    +            </code></pre>
    +        </p>
    +        <h3>Example Attribute Output</h3>
    +        <p>
    +            <pre><code>
    +    problemSection.act_04.observation.effectiveTime.low=20130711
    +    problemSection.act_04.observation.id.extension=121387536
    +    
problemSection.act_04.observation.id.root=2.16.840.1.113883.1.13.99999.999239
    +    problemSection.act_04.observation.statusCode.code=completed
    +    problemSection.act_04.observation.values.code=194828000
    +    
problemSection.act_04.observation.values.codeSystem=2.16.840.1.113883.6.96
    +    problemSection.act_04.observation.values.codeSystemName=SNOMED CT
    +    problemSection.act_04.observation.values.displayName=Angina (disorder)
    +    problemSection.act_04.observation.values.translations.code=413.9
    +    
problemSection.act_04.observation.values.translations.codeSystem=2.16.840.1.113883.6.103
    +    
problemSection.act_04.observation.values.translations.codeSystemName=ICD-9CM 
(diagnosis codes)
    +    
problemSection.act_04.observation.values.translations.displayName=Other and 
unspecified angina pectoris
    +    problemSection.act_04.statusCode.code=active
    +            </code></pre>
    +        </p>
    +        <h3>Example Parser Mapping</h3>
    +        <p>
    +            This processor is driven by a mapping file which specifies the 
element relationships. For example
    +            <pre><code>
    +    
org.openhealthtools.mdht.uml.cda.consol.impl.ProblemObservationImpl=id#element.ids\
    +        @values#element.values[0]\
    +        @statusCode#element.statusCode\
    +        @effectiveTime#element.effectiveTime\
    +        @negation#element.negationInd\
    +        @problemStatus#element.problemStatus
    +    
org.openhealthtools.mdht.uml.cda.consol.impl.ProblemStatusImpl=id#element.id\
    +        @code#element.code\
    +        @values#element.values[0]\
    +        @statusCode#element.statusCode
    +            </code></pre>
    +        </p>
    +        <h3>References</h3>
    +        <p>
    +            These mappings are defined as per the implementation guide -<a 
href="http://www.hl7.org/documentcenter/public/standards/dstu/CDAR2_IG_IHE_CONSOL_DSTU_R1dot1_2012JUL.zip";>HL7
 Implementation Guide for CDA® Release 2</a></br>
    +</br>
    +            CCDA sample file used in this bundle for testing is from <a 
href="https://github.com/chb/sample_ccdas/blob/master/Cerner%20Samples/Transition_of_Care_Referral_Summary.xml";>Cerner
 Sample - Transition of Care Referral Summary</a>
    --- End diff --
    
    Since the Cerner test file isn't included in the testing anymore, need to 
remove this from the additionalDetails.html


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to