Merge branch 'dev-michelle-updateLanguage' of https://github.com/onc-…

…healthit/site-ui-4 into dev-michelle-updateLanguage

src/components/archived/data/FAQ.json

@@ -10,11 +10,11 @@
     },
     {
       "question": "What are the key features of SITE?",
-      "answer": "SITE includes ONC Certification Tools, General Testing Tools, and Resources.  ONC Certification Tools include FHIR resources, C-CDA testing, clinical quality measure testing, electronic prescribing tools, public health reporting testing, and alternative testing. Our General Testing Tools include a suite of general testing tools, including the CPOE Evaluation Tool, IHE Testing Tools, Lantern Project, and the Inferno HL7 FHIR Validator.  In addition to this FAQ resource, videos and documentation help enhance your understanding of SITE."
+      "answer": "SITE includes ONC Certification Tools, General Testing Tools, and Resources.  ONC Certification Tools include FHIR® resources, C-CDA testing, clinical quality measure testing, electronic prescribing tools, public health reporting testing, and alternative testing. Our General Testing Tools include a suite of general testing tools, including the CPOE Evaluation Tool, IHE Testing Tools, Lantern Project, and the Inferno HL7® FHIR® Validator.  In addition to this FAQ resource, videos and documentation help enhance your understanding of SITE."
     },
     {
       "question": "How can I report issues or seek assistance on SITE?",
-      "answer": "Contact us at [email protected] or access our forum for the latest questions & answers. \nQuestions about the applicability of the initial set of standards, implementation specifications, and certification criteria should be directed to ONC at [email protected]. Questions about the functions and activities of the ONC-ATLs and ONC-ACBs should also be directed to ONC at [email protected]."
+      "answer": "Contact us at [email protected] or access our forum for the latest questions & answers. \nQuestions about the applicability of the initial set of standards, implementation specifications, and certification criteria should be directed to ASTP at [email protected]. Questions about the functions and activities of the ONC-ATLs and ONC-ACBs should also be directed to ASTP at [email protected]."
     }
   ],
   "Direct": [
@@ -267,7 +267,7 @@
       "answer": "No specific updates were made to the tool to remove the validation for the “No Known Problems”.\nAre you following the HL7 example at http://hl7-c-cda-examples.herokuapp.com/examples/view/7353a215efda8dfe3fbacb19abbb90756ce14bab"
     },
     {
-      "question": "Hoping to obtain some clarity around representing NDC codes for administered immunizations in the C-CDA.\n\nNDC is published as a standard for immunizations as a CCDS element and the ONC's CCDS companion guide cites that it's supported as a translational element accompanying the CVX code in CDA R2.1. Looking at the 2.1 IG, NDC is referenced within the Immunization Medication Information entry-level template with the Vaccine Clinical Drug value set stating: \"Value set intentionally defined from RXNORM (OID: 2.16.840.1.113883.6.88), comprised of those codes whose ingredients map to NDC codes that the CDC associates with CVX codes.\" Reading this and viewing the provided examples it appears as though the IG expects only RxNorm codes (not NDC) to be used as translational element entries mapping between an NDC and a CVX.\n\nNDC's are not actually included anywhere in the certification test data/validation for immunizations (only CVX), and I'm struggling to find any examples of their use for immunizations in C-CDA. Is there a specific expectation of how NDC codes are to be represented in C-CDA docs (if at all) to satisfy the ONC's CCDS standard?",
+      "question": "Hoping to obtain some clarity around representing NDC codes for administered immunizations in the C-CDA.\n\nNDC is published as a standard for immunizations as a CCDS element and the CCDS companion guide cites that it's supported as a translational element accompanying the CVX code in CDA R2.1. Looking at the 2.1 IG, NDC is referenced within the Immunization Medication Information entry-level template with the Vaccine Clinical Drug value set stating: \"Value set intentionally defined from RXNORM (OID: 2.16.840.1.113883.6.88), comprised of those codes whose ingredients map to NDC codes that the CDC associates with CVX codes.\" Reading this and viewing the provided examples it appears as though the IG expects only RxNorm codes (not NDC) to be used as translational element entries mapping between an NDC and a CVX.\n\nNDC's are not actually included anywhere in the certification test data/validation for immunizations (only CVX), and I'm struggling to find any examples of their use for immunizations in C-CDA. Is there a specific expectation of how NDC codes are to be represented in C-CDA docs (if at all) to satisfy the CCDS standard?",
       "answer": "The test data contains CVX because that is accompanied with a SHALL requirement in the C-CDA IG.\nSince the translation elements are having a conformance statement of “MAY” and not a “SHALL”, you could choose to use the NDC codes mapped to the CVX codes in the translation element as specified by the CCG."
     }
   ],
@@ -282,23 +282,23 @@
     },
     {
       "question": "How do we differentiate between a PRN medication and a Daily once frequency medication?",
-      "answer": "Right now, the presence of a 'precondition' with appropriate nullFlavor is an indicator for PRN without a precondition. If you have a precondition, that that is your precondition PRN - if this is a problem in your current live implementation, please come to HL7 SDWG (Thursday 10-12 PM ET - Agenda) - happy to discuss alternative approaches. \" QD = daily\" & \"PRN = As needed\"; You can have 'Daily with a specific precondition (e.g. Back pan) or 'Daily as-needed'\n(aka QD PRN). If you want to present an example with precondition, we are happy to have\nyou on the HL7 examples task force."
+      "answer": "Right now, the presence of a 'precondition' with appropriate nullFlavor is an indicator for PRN without a precondition. If you have a precondition, that that is your precondition PRN - if this is a problem in your current live implementation, please come to HL7® SDWG (Thursday 10-12 PM ET - Agenda) - happy to discuss alternative approaches. \" QD = daily\" & \"PRN = As needed\"; You can have 'Daily with a specific precondition (e.g. Back pan) or 'Daily as-needed'\n(aka QD PRN). If you want to present an example with precondition, we are happy to have\nyou on the HL7® examples task force."
     },
     {
       "question": "We're having an issue Receiving the Documents and saving to the EHR. We have code to check for a document ID which has been sent in the past. Is there a way we could set the unique document ID in the test so that we can import the files more easily?",
       "answer": "The ETT uses a symbolic ID (\"Document01\") in the metadata to identify the attached document:<rim:ExtrinsicObject id=\"Document01\" mimeType=\"text/xml\" objectType=\"urn:uuid:7edca82f-054d-47f2-a032-9b2a5b5186c1\">\nIt is incumbent upon the receiving registry in a provide and register transaction to turn the symbolic ID into a UUID of their choosing. In IHE ITI, Volume 2b, see Section 3.42.4.1.3.7 UUIDs and Symbolic Ids: \"If a field is formatted as a symbolic Id in the Submission Request, the Document Registry shall replace it with newly generated, properly formatted UUIDs upon acceptance of the submission. If the same symbolic ID appears more than once in the Submission Request, it shall be replaced with the same generated UUID.\" The receiving system must be able to handle symbolic IDs in accordance with the base IHE specifications."
     },
     {
       "question": "We're getting an error message while trying to validate a C-CDA file- any suggestions?",
-      "answer": "All prescribable medication formulations are represented using either a \"generic\" or \"brand-specific\" concept. This includes RxNorm codes whose Term Type is SCD (semantic clinical drug), SBD (semantic brand drug), GPCK (generic pack), BPCK (brand pack), SCDG (semantic clinical drug group), SBDG (semantic brand drug group), SCDF (semantic clinical drug form), or SBDF (semantic brand drug form). It does not include the PSN term type, hence the error. If PSN needs to be included, it should be an ERRATA through HL7."
+      "answer": "All prescribable medication formulations are represented using either a \"generic\" or \"brand-specific\" concept. This includes RxNorm codes whose Term Type is SCD (semantic clinical drug), SBD (semantic brand drug), GPCK (generic pack), BPCK (brand pack), SCDG (semantic clinical drug group), SBDG (semantic brand drug group), SCDF (semantic clinical drug form), or SBDF (semantic brand drug form). It does not include the PSN term type, hence the error. If PSN needs to be included, it should be an ERRATA through HL7®."
     },
     {
       "question": "For Negative Testing CCDS samples 2 and 3, there is a SNOMED code \"27171005\" which is being validated in the ETT Message Validator as a LOINC code and throwing an error. It appears that this is a valid SNOMED code in the results section of a procedure. Will the ETT Message Validator be updated to address this issue?",
       "answer": "Negative Testing which is being performed as part of the b1 capability is to ensure that the System Under Test (SUT) is more robust and is able to receive and parse C-CDA’s more effectively including the CCDS data elements. All of the CCDS vocabulary requirements that are enforced for normal b1 sample XML files are valid for negative testing also."
     },
     {
       "question": "I tried to understand the certification criteria but got stuck with understanding 170.315(h)(1) & (h)(2). I don't understand why h1, looks like h2 is covering h1. I have a couple of questions:\n1. What is an edge system and how to implement it? DO I HAVE TO for this MU3 Certification?\n2. As of my knowledge, a HISP can be implemented by using Direct project JAVA RI, but I don't understand what an edge protocol is and how to implement?\n3. All documents in the \"Implementation Guide for Delivery Notification in Direct V 1.1\" and the \"Applicability Statement for Secure Health Transport V 1.2\" are talking about HISP-SMTP, Edge-SMTP, and SOAP protocol. What is the deference?",
-      "answer": "The definition of an Edge system and Edge protocols are defined in Implementation Guide for Direct Edge Protocols Version 1.1 which is available here:\nhttps://www.healthit.gov/sites/default/files/implementationguidefordirectedgeprotocolsv1_1.pdf. \n Questions regarding the Certification Program should be addressed via email to: [email protected]. You will also discover information at this link: https://www.healthit.gov/policy-researchers-implementers/2015-edition-test-method"
+      "answer": "The definition of an Edge system and Edge protocols are defined in Implementation Guide for Direct Edge Protocols Version 1.1 which is available here:\nhttps://www.healthit.gov/sites/default/files/implementationguidefordirectedgeprotocolsv1_1.pdf. \n Questions regarding the ONC Certification Program should be addressed via email to: [email protected]. You will also discover information at this link: https://www.healthit.gov/policy-researchers-implementers/2015-edition-test-method"
     },
     {
       "question": "Attached is an Edge sample file with UNKNOWN for patient race and ethnicity. I have tried but could not find UNKNOWN anywhere in OMB/CDC race and ethnicity value set codes. I have tried several ways, but it is giving data validation error. Please guide us from where i can find code for UNKNOWN race and ethnicity. Is there an issue in sample file data ??",

src/components/archived/data/faq.md

@@ -558,7 +558,7 @@ I believe the application is hard-coded to look for those particular folders in
 
       * A: No specific updates were made to the tool to remove the validation for the “No Known Problems”.
 
-  Are you following the HL7 example at http://hl7-c-cda-examples.herokuapp.com/examples/view/7353a215efda8dfe3fbacb19abbb90756ce14bab
+  Are you following the HL7® example at http://hl7-c-cda-examples.herokuapp.com/examples/view/7353a215efda8dfe3fbacb19abbb90756ce14bab
 
 - Q: Hoping to obtain some clarity around representing NDC codes for administered immunizations in the C-CDA.
 
@@ -592,9 +592,9 @@ Because that is not a domain that we manage, our system is rejecting the XDR mes
 
 - Q: How do we differentiate between a PRN medication and a Daily once frequency medication?
 
-  - A: Right now, the presence of a ‘precondition’ with appropriate nullFlavor is an indicator for PRN without a precondition. If you have a precondition, that that is your precondition PRN – if this is a problem in your current live implementation, please come to HL7 SDWG (Thursday 10-12 PM ET - Agenda) – happy to discuss alternative approaches. " QD = daily" & "PRN = As needed"; You can have ‘Daily with a specific precondition (e.g. Back pan) or ‘Daily as-needed’
+  - A: Right now, the presence of a ‘precondition’ with appropriate nullFlavor is an indicator for PRN without a precondition. If you have a precondition, that that is your precondition PRN – if this is a problem in your current live implementation, please come to HL7® SDWG (Thursday 10-12 PM ET - Agenda) – happy to discuss alternative approaches. " QD = daily" & "PRN = As needed"; You can have ‘Daily with a specific precondition (e.g. Back pan) or ‘Daily as-needed’
     (aka QD PRN). If you want to present an example with precondition, we are happy to have
-    you on the HL7 examples task force.
+    you on the HL7® examples task force.
 
 - Q: The previous test data (v9) had medications that seemed to fall either within the admission (6/22/15-6/24/15) or to be discharge medications (beginning 6/24/15 with various end dates). The v10 test data changed the dates. Was there a rationale for this change? Are the medications that start during the admission but continue after it (for example, 6/22/15-6/30/15) intended to be prescriptions or inpatient orders?
 
@@ -624,7 +624,7 @@ Because that is not a domain that we manage, our system is rejecting the XDR mes
 
 - Q: We’re getting an error message while trying to validate a C-CDA file- any suggestions?
 
-  - A: All prescribable medication formulations are represented using either a "generic" or "brand-specific" concept. This includes RxNorm codes whose Term Type is SCD (semantic clinical drug), SBD (semantic brand drug), GPCK (generic pack), BPCK (brand pack), SCDG (semantic clinical drug group), SBDG (semantic brand drug group), SCDF (semantic clinical drug form), or SBDF (semantic brand drug form). It does not include the PSN term type, hence the error. If PSN needs to be included, it should be an ERRATA through HL7.
+  - A: All prescribable medication formulations are represented using either a "generic" or "brand-specific" concept. This includes RxNorm codes whose Term Type is SCD (semantic clinical drug), SBD (semantic brand drug), GPCK (generic pack), BPCK (brand pack), SCDG (semantic clinical drug group), SBDG (semantic brand drug group), SCDF (semantic clinical drug form), or SBDF (semantic brand drug form). It does not include the PSN term type, hence the error. If PSN needs to be included, it should be an ERRATA through HL7®.
 
 - Q: For Negative Testing CCDS samples 2 and 3, there is a SNOMED code "27171005" which is being validated in the ETT Message Validator as a LOINC code and throwing an error. It appears that this is a valid SNOMED code in the results section of a procedure. Will the ETT Message Validator be updated to address this issue?
 

src/components/c-cda/CCDAHome.tsx

@@ -35,7 +35,7 @@ const CCDAHome = () => {
       />
       {/* Main Content */}
       <Container>
-        <SectionHeader header={'C-CDA Validators'} subHeader={'The latest C-CDA validators from ONC'} />
+        <SectionHeader header={'C-CDA Validators'} subHeader={'The latest C-CDA validators from ASTP'} />
         <Box display={'flex'} width={'100%'} justifyContent={'space-between'}>
           <CardWithImage
             title={'C-CDA Validator: USCDI v3'}

src/components/c-cda/scorecard/next-steps/ScorecardTabs.tsx

@@ -143,7 +143,7 @@ export default function ScorecardTabs({ rubric }: ScorecardTabsProps) {
             {rubric.exampleTaskForceLinks.map((tfLink, index) => (
               <ListItem sx={{ display: 'list-item' }} key={index}>
                 <ListItemText
-                  primary="Related HL7 C-CDA Task Force example"
+                  primary="Related HL7® C-CDA Task Force example"
                   primaryTypographyProps={{ fontWeight: 'bold' }}
                   sx={{ pb: 3 }}
                 />

src/components/c-cda/validation/uscdi-v1/USCDIV1Validator.tsx

@@ -22,7 +22,7 @@ export default function USCDIV1Validator() {
           </Link>,
         ]}
         heading={'C-CDA USCDI V1 Validator'}
-        // TODO: Get a unique description from the ONC for USCDI V1
+        // TODO: Get a unique description from ASTP for USCDI V1
         description={
           <>
             The C-CDA R2.1 Validator is a tool used to check if electronic health documents comply with the Clinical

src/components/c-cda/validation/uscdi-v3/USCDIV3Validator.tsx

@@ -22,7 +22,7 @@ export default function USCDIV3Validator() {
           </Link>,
         ]}
         heading={'C-CDA USCDI V3 Validator'}
-        // TODO: Get a unique description from the ONC for USCDI V3
+        // TODO: Get a unique description from ASTP for USCDI V3
         description={
           <>
             The C-CDA R2.1 Validator is a tool used to check if electronic health documents comply with the Clinical

src/components/cqmt/CqmHome.tsx

@@ -33,7 +33,7 @@ const CqmHome = () => {
         description={
           <>
             {
-              "Cypress, the official testing tool for EHR Certification under ONC's 2014 and 2015 Certification Editions, ensures precise evaluation of Clinical Quality Measures (CQM) in Electronic Health Records. Tailored for both EHR vendors and Authorized Testing Labs, Cypress, sponsored by the Office of the National Coordinator for Health IT and developed by The MITRE Corporation, facilitates rigorous and repeatable testing for accurate calculation of CQMs for Eligible Providers and Hospitals."
+              "Cypress, the official testing tool for EHR Certification under ONC's 2014 and 2015 Certification Editions, ensures precise evaluation of Clinical Quality Measures (CQMs) in Electronic Health Records(EHRs). Tailored for both EHR vendors and Authorized Testing Labs, Cypress, sponsored by ASTP and developed by The MITRE Corporation, facilitates rigorous and repeatable testing for accurate calculation of CQMs for Eligible Providers and Hospitals."
             }
           </>
         }
@@ -74,7 +74,7 @@ const CqmHome = () => {
               cardImage={cypressImagery}
               cardHeader={'Rigorous & repeatable testing of Electronic Health Records'}
               description={
-                'Cypress is the rigorous and repeatable testing tool of Electronic Health Records (EHR) and EHR modules in calculating eCQMs used by CMS’s Quality Reporting Programs. The Cypress tool is open source and freely available for use or adoption by the health IT community including EHR vendors and testing labs. Cypress serves as the official testing tool for the EHR Certification program supported by the Office of the National Coordinator for Health IT (ONC).'
+                'Cypress is the rigorous and repeatable testing tool of Electronic Health Records (EHRs) and EHR modules in calculating eCQMs used by CMS’s Quality Reporting Programs. The Cypress tool is open source and freely available for use or adoption by the health IT community including EHR vendors and testing labs. Cypress serves as the official testing tool for the EHR Certification program supported by the Assistant Secretary for Technology Policy (ASTP).'
               }
               pathname={'https://www.healthit.gov/cypress/'}
               maxWidth={900}
@@ -104,7 +104,7 @@ const CqmHome = () => {
             />
             <VerticalCard
               title={'Cypress Issue Tracker'}
-              description={'Track questions and issue that Cypress supports.'}
+              description={'Track questions and issues that Cypress supports.'}
               buttonTitle={'TRACK your question'}
               buttonIcon={<TrackChangesIcon />}
               buttonHref={'https://jira.oncprojectracking.org/browse/CYPRESSef'}