Create custom value sets / code systems for DocumentReference

enjoysparkling commented 1 year ago

Tasks

[x] Identify elements needing customization
[x] Collect codes, displays, and definitions for each element
[x] Create custom CodeSystem(s)
[x] Create custom ValueSet(s)
[x] Bring in derived resource profile
[ ] Bind ValueSet(s) to profile
[ ] Update documentation

Elements that need custom ValueSet (VS) and Code System (CS)

[ ] .category ~~.type~~
- [ ] - MAP LOINC codes - will need to include ADDITIONAL ValueSet with the Signal "Classifications". Ideally, these concepts should be mapped to LOINC codes
- [x] - Create expanded ValueSet and bind it

enjoysparkling commented 1 year ago

Latest list for File Classification:

referral
assessment request
treatment record (would include treatment plan, progress notes, discharge plan, discharge summary, release of information, client monthly progress report)
service authorizations
quality monitoring (would include critical incident, grievance, waitlist tracker, utilization review, training report, denial report)
data submission (would include compliance reports for MSO, episodic data for CCS)
invoice
Audit Requested Records
Credential Requested Records
Service Organization Feedback

arunsundar-m commented 1 year ago

@enjoysparkling @Gokulsignal It looks like the mapping with LOINC codes has to be done by the business, we can create a custom valueset as we do it for other resources

https://loinc.org/search/?t=1&s=attach https://loinc.org/search/?t=1&s=document

I tried searching with the above keywords but can't map to the above list.

Gokulsignal commented 1 year ago

Value set and Code System is created for the "Signal File Repo Classification" under the Document Reference.

https://github.com/enjoysparkling/signal-mso-fhir-profiles/pull/104

valueset-signal-filerepo-classification codesystem-signal-filerepo-classification

Below are the Code and Display values as part of the Signal specific drop downs. LIONC codes are expanded under the Expansion.Contain element

Kindly review the same and let us know if any changes required.

arunsundar-m commented 1 year ago

@enjoysparkling @Gokulsignal I have made the naming convention changes, fixed the forge issues for code system and valueset for file-repo-classification #https://github.com/enjoysparkling/signal-mso-fhir-profiles/pull/104/commits/65d1dd0f81282199f2d8d2e92ecb852ae92073c5

jfabrizio329 / signal-mso-fhir-profiles

Create custom value sets / code systems for DocumentReference #89