Use of value sets to configure Provider Management API

[laskeyk]

FHIR has the concept of value sets to identify sets of valid values that can be assigned. For example of how this applies, in last week's discussion, Verification Type can be assigned the values Initial or Revalidation; the etc. indicates future uncertainty. Such defines a value set. The suggestion here is to use value sets to facilitate configuring choices, especially where we don't necessarily know the valid values or where the values are likely to change. For example, if the provider needs to enroll in Utah, a (configuration controlled) value set would identify PSV Services relevant to Utah and API input values would depend on the inputs needed for the services chosen from the Utah list. Processing somewhere in the identified components for our process flow generates desired information, and the Provider Management API will get the information to Provider Management without worrying where the information is generated or who needs to use that API.

Further details follow on inputs and the places value sets can play a role..

Provider Enrollment API inputs

• Jurisdiction (state, etc.) for which screening is to be done (from value set)
• Verification Type (Initial, Revalidation, etc. from value set)
• PSV Services to perform (list from value set based on Jurisdiction, Verification Type)
• Enrollment inputs or otherwise accessed values (e.g., from authoritative source)
  o As required or optional from value set of common inputs across all Jurisdictions for all Verification Types (e.g., possibly some form of name, address)
  o Aggregate of required or optional from value sets of inputs for each chosen PSV Service (based on Jurisdiction, Verification Type)

Internally generated values

• Trace ID (Tracking for audit and other internal process purposes)
• PSV Status (Complete, Incomplete, Fail from value set)
• Timestamp when PSV Status generated
• PSV Details (PSV Service (including version), PSV Result Category (from value set), timestamp when PSV Result generated

Supporting (assuming configuration controlled, maintained history) documentation

• Identified value sets
• PSV Service configuration with information such as data sources used

Provider Management API Inputs

• Provider Enrollment inputs (assuming needed for audit)
• Internally generated values that are generated outside of Provider Management
• Anything else needed for audit (Audit resource?) or information desired by enrollment initiator

To do

• Specify initial value sets indicated
• Document controlled configurations