This page is part of the US Core (v6.0.0: STU6) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/us/core/ValueSet/us-core-pregnancy-intent | Version: 6.0.0 | |||
Active as of 2022-09-29 | Computable Name: USCorePregnancyIntentCodes | |||
Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License |
This value set includes SNOMED CT codes and the HL7 V3 code for the concept “unknown”.
References
This value set uses SMOMED CT codes which are available in VSAC. LOINC also provides an example list LL4053-6 for the code 86645-9 (Pregnancy intention in the next year - Reported) used in the US Core Observation Pregnancy Intent Profile. The table below provides implementers with a concept mapping between these codes.
SNOMED CT | SNOMED CT Preferred Name | LOINC Answer ID | Answer |
---|---|---|---|
454381000124105 | Not sure of desire to become pregnant (finding) | LA14072-5 | Unsure |
454391000124108 | Ambivalent about becoming pregnant (finding) | LA26439-2 | I’m OK either way |
454401000124105 | No desire to become pregnant (finding) | LA26440-0 | No, I don’t want to become pregnant |
454411000124108 | Wants to become pregnant (finding) | LA26438-4 | Yes, I want to become pregnant |
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/v3-NullFlavor
Code | Display | Definition |
UNK | Unknown | **Description:**A proper value is applicable, but not known. **Usage Notes**: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless: 1. Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 2. Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.) |
This value set contains 5 concepts
Expansion based on NullFlavor v2.1.0 (CodeSystem)
Code | System | Display | Definition |
454381000124105 | http://snomed.info/sct | Not sure of desire to become pregnant (finding) | |
454391000124108 | http://snomed.info/sct | Ambivalent about becoming pregnant (finding) | |
454401000124105 | http://snomed.info/sct | No desire to become pregnant (finding) | |
454411000124108 | http://snomed.info/sct | Wants to become pregnant (finding) | |
UNK | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | Unknown | **Description:**A proper value is applicable, but not known. Usage Notes: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless:
|
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 |