This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4
Vocabulary Work Group | Maturity Level: N/A | Standards Status: Informative |
Raw JSON (canonical form + also see JSON Format Specification)
Definition for Code System ObservationCategoryCodes
{ "resourceType" : "CodeSystem", "id" : "secondary-finding", "meta" : { "lastUpdated" : "2019-12-31T21:03:40.621+11:00", "profile" : ["http://hl7.org/fhir/StructureDefinition/shareablecodesystem"] }, "text" : { "status" : "generated", "div" : "<div>!-- Snipped for Brevity --></div>" }, "url" : "http://hl7.org/fhir/secondary-finding", "identifier" : [{ "system" : "urn:ietf:rfc:3986", "value" : "urn:oid:2.16.840.1.113883.4.642.1.1286" }], "version" : "4.2.0", "name" : "ObservationCategoryCodes", "title" : "Observation Category Codes", "status" : "draft", "experimental" : false, "publisher" : "FHIR Project team", "contact" : [{ "telecom" : [{ "system" : "url", "value" : "http://hl7.org/fhir" }] }], "description" : "Codes to denote a guideline or policy statement.when a genetic test result is being shared as a secondary finding.", "caseSensitive" : true, "valueSet" : "http://hl7.org/fhir/ValueSet/secondary-finding", "content" : "complete", "concept" : [{ "code" : "acmg-version1", "display" : "ACMG Version 1", "definition" : "First release (2013): ACMG Recommendations for Reporting of Incidental Findings in Clinical Exome and Genome Sequencing. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3727274/" }, { "code" : "acmg-version2", "display" : "ACMG Version 2", "definition" : "Second release (2016): Recommendations for reporting of secondary findings in clinical exome and genome sequencing, 2016 update (ACMG SF v2.0): a policy statement of the American College of Medical Genetics and Genomics. https://www.ncbi.nlm.nih.gov/pubmed/27854360" }] }
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.