Difference between revisions of "Proposal: AdministrativeContactRoleType"
| Line 14: | Line 14: | ||
|| Date submitted: July 23, 2009 | || Date submitted: July 23, 2009 | ||
|- | |- | ||
| − | || Editor/Author: '' | + | || Editor/Author: ''Lloyd McKenzie'' |
|| Sponsor Status: ''Pending'' | || Sponsor Status: ''Pending'' | ||
|- | |- | ||
| Line 24: | Line 24: | ||
== Summary of Vocabulary changes == | == Summary of Vocabulary changes == | ||
| − | + | Create a concept domain called AdministrativeContactRoleType and add additional concepts to existing code system. | |
{|width=100% cellspacing=0 cellpadding=2 border=1 | {|width=100% cellspacing=0 cellpadding=2 border=1 | ||
| Line 36: | Line 36: | ||
|| D | || D | ||
|| Concept Domains | || Concept Domains | ||
| − | || '' | + | || ''1'' |
|| ''Number'' | || ''Number'' | ||
|| ''Number'' | || ''Number'' | ||
| Line 45: | Line 45: | ||
|| ''Number'' | || ''Number'' | ||
|| ''Number'' | || ''Number'' | ||
| − | || '' | + | || ''1'' |
|- | |- | ||
|- | |- | ||
|| C | || C | ||
|| Concept codes in a code system | || Concept codes in a code system | ||
| − | || '' | + | || ''6'' |
|| ''Number'' | || ''Number'' | ||
|| ''Number'' | || ''Number'' | ||
| Line 64: | Line 64: | ||
|| B | || B | ||
|| Context Bindings | || Context Bindings | ||
| − | || '' | + | || ''1'' |
|| ''Number'' | || ''Number'' | ||
|| ''Number'' | || ''Number'' | ||
| Line 78: | Line 78: | ||
|bgcolor="#aaaaff" align=center| '''AFFECTED ENTITIES OF INTEREST TO ORG''' | |bgcolor="#aaaaff" align=center| '''AFFECTED ENTITIES OF INTEREST TO ORG''' | ||
|- | |- | ||
| − | || '' | + | || ''Patient Administration'' |
| − | || '' | + | || ''Pending'' |
| − | || '' | + | || ''Service Delivery Location Detail:ContactParty.code'' |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
|} | |} | ||
== Issue == | == Issue == | ||
| − | + | There’s a need to capture administrative contacts for service delivery locations and differentiate what type of contact they are. | |
== Recommendation Details == | == Recommendation Details == | ||
| − | + | Create a concept domain called AdministrativeContactRoleType under RoleCode with the following definition: | |
| + | “Indicates the primary purpose or type of person intended to be reached using a set of contact information. I.e. the categories that may be displayed in a phone directory listing. | ||
| + | |||
| + | Examples: | ||
| + | • Admitting | ||
| + | • Billing | ||
| + | • Test Results | ||
| + | Add the following new codes to the RoleCode code system under _AdministrativeContactRoleType: | ||
| + | |||
| + | |||
| + | {|width=100% cellspacing=0 cellpadding=2 border=1 | ||
| + | |- | ||
| + | |bgcolor="#aaaaff" align=center| '''Code''' | ||
| + | |bgcolor="#bbbbff" align=center| '''Concept''' | ||
| + | |bgcolor="#aaaaff" align=center| '''Description''' | ||
| + | |- | ||
| + | || ADMIT | ||
| + | || Admitting | ||
| + | || Contact for admissions or pre-admission department | ||
| + | |- | ||
| + | |- | ||
| + | || FIN | ||
| + | || Finance | ||
| + | || Contact for financial administration department | ||
| + | |- | ||
| + | |- | ||
| + | || PATREL | ||
| + | || Patient Relations | ||
| + | || Contact for Patient Relations and/or Referrals department | ||
| + | |- | ||
| + | |- | ||
| + | || INFO | ||
| + | || Information | ||
| + | || Contact for general information inquiries | ||
| + | |- | ||
| + | |- | ||
| + | || AFTHRS | ||
| + | || After Hours | ||
| + | || Contact for inquiries outside of regular business hours | ||
| + | |- | ||
| + | |- | ||
| + | || RESULTS | ||
| + | || Test Results | ||
| + | || Contact for test results | ||
| + | |-|} | ||
=== RIM Recommendation(s) === | === RIM Recommendation(s) === | ||
| Line 109: | Line 148: | ||
== Recommended Action Items == | == Recommended Action Items == | ||
*MnM to implement the proposed solution | *MnM to implement the proposed solution | ||
| − | + | ||
==Discussion== | ==Discussion== | ||
Revision as of 15:42, 23 July 2009
(This is a template. Do not edit. Copy and paste its source to a new page)
Editing of harmonization proposals prior to a harmonization meeting is restricted to the proposal submitter and the co-chairs of the steward comittee. Other changes will be undone. Please add comments to the "discussion" page associated with this proposal.
| Recommendation for HL7 RIM Change and/or Vocabulary changes | RECOMMENDATION ID: |
| Sponsored by: Patient Administration | Approval date by sponsor: TBD |
| Revision (# and date): #1, July 23, 2009 | Date submitted: July 23, 2009 |
| Editor/Author: Lloyd McKenzie | Sponsor Status: Pending |
| PROPOSALNAME: AdministrativeContactRoleType changes |
Contents
Summary of Vocabulary changes
Create a concept domain called AdministrativeContactRoleType and add additional concepts to existing code system.
| Abbrev. | Description | # to Add | # to Remove | # to Change |
| D | Concept Domains | 1 | Number | Number |
| S | Code Systems | Number | Number | 1 |
| C | Concept codes in a code system | 6 | Number | Number |
| V | Value sets | Number | Number | Number |
| B | Context Bindings | 1 | Number | Number |
Position of Concerned Organizations
REQUIRED - This table should contain one row for each organization/WG affected by the recommendation.
| ORG.NAME | RECOMMENDATION APPROVAL STATUS | AFFECTED ENTITIES OF INTEREST TO ORG |
| Patient Administration | Pending | Service Delivery Location Detail:ContactParty.code |
Issue
There’s a need to capture administrative contacts for service delivery locations and differentiate what type of contact they are.
Recommendation Details
Create a concept domain called AdministrativeContactRoleType under RoleCode with the following definition: “Indicates the primary purpose or type of person intended to be reached using a set of contact information. I.e. the categories that may be displayed in a phone directory listing.
Examples: • Admitting • Billing • Test Results
Add the following new codes to the RoleCode code system under _AdministrativeContactRoleType:
RIM Recommendation(s)
Vocabulary Recommendation(s)
Please use the fully specified names when inserting/adding/changing vocabularies, including full parentage of the vocabulary.
Rationale
Any additional information needed to understand, evaluate or implement the recommendation, such as model fragments or other context that demonstrates use of the requested change. Include implications.
Recommended Action Items
- MnM to implement the proposed solution
Discussion
Resolution
NOTE: This template puts this proposal in the "Harmonization Proposal" Wiki Category. Once the proposal has been discussed and the resolution has been aded, please update the Category statement to put the proposal in the "Discussed Harmonization Proposal". The "Harmonization Proposal" Wiki Category is for OPEN non-discussed proposals only.
| Code | Concept | Description |
| ADMIT | Admitting | Contact for admissions or pre-admission department |
| FIN | Finance | Contact for financial administration department |
| PATREL | Patient Relations | Contact for Patient Relations and/or Referrals department |
| INFO | Information | Contact for general information inquiries |
| AFTHRS | After Hours | Contact for inquiries outside of regular business hours |
| RESULTS | Test Results | Contact for test results |
