Source: https://www.healthit.gov/test-method/family-health-history
Timestamp: 2019-04-24 12:01:43+00:00

Document:
Enable a user to record, change, and access a patient's family health history in accordance with the familial concepts or expressions included in, at a minimum, the version of the standard in §170.207(a)(4).
Added clarification for the testing and certification of “familial concepts or expressions”.
Removed “unstructured/free text recording” clarification.
Further clarification provided for the structured coding and representation of familial relationship.
Privacy and Security: This certification criterion was adopted at § 170.315(a)(12). As a result, an ONC-ACB must ensure that a product presented for certification to a § 170.315(a) “paragraph (a)” criterion includes the privacy and security criteria (adopted in § 170.315(d)) within the overall scope of the certificate issued to the product.
The privacy and security criteria (adopted in § 170.315(d)) do not need to be explicitly tested with this specific paragraph (a) criterion unless it is the only criterion for which certification is requested.
As a general rule, a product presented for certification only needs to be presented once to each applicable privacy and security criterion (adopted in § 170.315(d)) so long as the health IT developer attests that such privacy and security capabilities apply to the full scope of capabilities included in the requested certification. However, exceptions exist for § 170.315(e)(1) “VDT” and (e)(2) “secure messaging,” which are explicitly stated.
Technical outcome – The health IT permits users to record, change, and access a patient’s family health history (FHH) according to the September 2015 Release of SNOMED CT®, U.S. Edition.
We provide the following OID to assist developers in the proper identification and exchange of health information coded to certain vocabulary standards.
Our intent with “familial concepts and expressions” is to focus on the first degree relative’s diagnosis. For testing and certification, at a minimum, a system must be able to demonstrate that it can record, change, and access this diagnosis and the familial relationship in a codified manner using SNOMED CT®. The developer has the flexibility to determine how the system will represent the codified familial relationship, pre- or post-coordinated.

References: §170
 § 170
 § 170
 § 170
 § 170
 § 170
 § 170