Australian Digital Health Agency FHIR Implementation Guide, published by Australian Digital Health Agency. This guide is not an authorized publication; it is the continuous build for version 1.2.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/AuDigitalHealth/ci-fhir-r4/ and changes regularly. See the Directory of published versions

ValueSet: Apgar Reflex Irritability Finding (Experimental)

Official URL: http://ns.electronichealth.net.au/fhir/ValueSet/apgarreflexirritabilityfinding-1 Version: 0.1.0
Draft as of 2024-12-19 Computable Name: ApgarReflexIrritabilityFinding

Copyright/Legal: This resource contains content from LOINC™ (http://loinc.org). The LOINC Table, LOINC Table Core, LOINC Panels and Forms File, LOINC Answer File, LOINC Part File, LOINC Group File, LOINC Document Ontology File, LOINC Hierarchies, LOINC Linguistic Variants File, LOINC/RSNA Radiology Playbook, and LOINC/IEEE Medical Device Code Mapping Table are copyright © 1995-2017, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license.

The Apgar Reflex Irritability Finding value set includes values that cover findings of Apgar reflex irritability (response to stimulus, grimace).

References

Logical Definition (CLD)

Generated Narrative: ValueSet apgarreflexirritabilityfinding-1

 

Expansion

No Expansion for this valueset (not supported by Publication Tooling)

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code