This page is part of the Da Vinci Patient Cost Transparency Implementation Guide (v0.1.0: STU 1 Draft) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 2.0.0. For a full list of available versions, see the Directory of published versions
Summary
| Defining URL: | http://hl7.org/fhir/us/davinci-pct/ValueSet/PCTSubjectToMedicalMgmtReasonVS |
| Version: | 0.1.0 |
| Name: | PCTSubjectToMedicalMgmtReasonVS |
| Title: | PCT Subject-To-Medical-Management Reason Value Set - locally defined for testing purpose; an external FHIR value set will be created through the HL7 Terminology (THO) process to replace this value set |
| Status: | Active as of 12/4/21 9:54 PM |
| Definition: | Codes for the classification of subject-to-medical-management reasons |
| Publisher: | HL7 International - Financial Management Work Group |
| Copyright: | This Valueset is not copyrighted. |
| Source Resource: | XML / JSON / Turtle |
References
http://hl7.org/fhir/us/davinci-pct/CodeSystem/PCTSubjectToMedicalMgmtReasonCS
This value set contains 4 concepts
Expansion based on PCT Subject-To-Medical-Management Reason Code System v0.1.0 (CodeSystem)
All codes in this table are from the system http://hl7.org/fhir/us/davinci-pct/CodeSystem/PCTSubjectToMedicalMgmtReasonCS
| Code | Display | Definition |
| concurrent-review | Concurrent Review | Concurrent Review |
| prior-auth | Prior Authorization | Prior Authorization |
| step-therapy | Step Therapy | Step Therapy |
| fail-first | Fail-First | Fail-First |
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 |
| Source | 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 |