Direct Standard Clause Samples

Direct Standard. The Direct Standard is a set of protocols and technical specifications, as defined by 45 CFR Part 170, Section 170.202(a), and endorsed by the Office of the National Coordinator for Health IT (ONC), to enable the secure exchange of health information over the Internet. Participant, its CA, and RA shall follow the Direct Standard, and any amendments to the Direct Standard, for secure messaging when transmitting or receiving (or facilitating the transmission or receipt of) Basic Messages under this Agreement.
View SourceView Similar (6)
Direct Standard. The Direct Standard is a set of protocols and technical specifications, as defined by 45 CFR Part 170, Section 170.202 (a), and endorsed by the Office of the National Coordinator for Health IT (ONC), to enable the secure exchange of health information over the Internet. CA/RA shall follow the Direct Standard, and any amendments to the Direct Standard, for secure messaging when supporting Participant’s HISP services in connection with the DirectTrust Accredited Trust Anchor Bundle under the DirectTrust FSA. “Basic Message,” as used in this Addendum, means a message used to send a variety of structured or unstructured content in accordance with the Direct Standard, which incorporates by reference the Applicability Statement for Secure Health Transport, Version 1.1, July 10, 2012, available at: ▇▇▇▇://▇▇▇▇▇▇▇▇.▇▇▇.▇▇▇/portal/▇▇▇▇▇▇.▇▇/community/healthit_hhs_gov direct_project/33381 and any amendments.
View SourceView Similar (3)

Related to Direct Standard

  • Meets Standard The school materially complies with applicable laws, rules, regulations and provisions of the charter contract relating to health and safety, including but not limited to: • Health clearances and immunizations • Prohibiting smoking on campus • Appropriate student health services • Safety plan

  • Hot Weather Guidelines For the purposes of site based discussions regarding the need to plan and perform work during expected periods of hot weather, the following issues shall be considered in conjunction with proper consideration of Occupational Health and Safety issues.

  • Applicable Standards The requirements and guidelines of NERC, the Applicable Regional Entity, and the Control Area in which the Customer Facility is electrically located; the PJM Manuals; and Applicable Technical Requirements and Standards.

  • Does Not Meet Standard The school's proficiency rate in math is 1 - 10 percentage points lower than the state average. 15 - 29 0 Falls Far Below Standard: The school's proficiency rate in math is 11 or more percentage points lower than the state average. 0 - 14 0 Notes The state average will be determined using the same grade set as is served by the public charter school. 0 Comparison to State Exceeds Standard: The school's proficiency rate in ELA exceeds the state average by 16 percentage points or more. 50 0 Meets Standard: The school's proficiency rate in ELA is equal to the state average, or exceeds it by 1 - 15 percentage points. 30 - 45 0 Does Not Meet Standard: The school's proficiency rate in ELA is 1 - 10 percentage points lower than the state average. 15 - 29 0 Falls Far Below Standard: The school's proficiency rate in ELA is 11 or more percentage points lower than the state average. 0 - 14 0 Notes The state average will be determined using the same grade set as is served by the public charter school. 0

  • File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in ▇▇▇ ▇▇▇▇, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.