Protocols for Clinical Registry Extraction and Data Submission (CREDS) IG
1.0.0-ballot - STU1 United States of America flag

This page is part of the Protocols for Clinical Registry Extraction and Data Submission (CREDS) IG (v1.0.0-ballot: STU1 Ballot 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions

ValueSet: Seattle Angina Answers (Experimental)

Official URL: http://hl7.org/fhir/us/registry-protocols/ValueSet/SeattleAnginaAs Version: 1.0.0-ballot
Active as of 2023-03-29 Computable Name: SeattleAnginaAs

Copyright/Legal: This material contains content from LOINC (http://loinc.org). LOINC is copyright © 1995-2020, 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. LOINC® is a registered United States trademark of Regenstrief Institute, Inc

LOINC codes for the answers to SA Questions

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

 

Expansion

This value set contains 6 concepts

Expansion based on Loinc v2.73

CodeSystemDisplay
  LA28518-1http://loinc.org4 or more times per day
  LA25000-3http://loinc.org1-3 times per day
  LA27770-9http://loinc.org3 or more times per week but not every day
  LA13834-9http://loinc.org1-2 times per week
  LA27722-0http://loinc.orgLess than once a week
  LA28522-3http://loinc.orgNone over the past 4 weeks

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