This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Proposal: AdministrativeContactRoleType"

From HL7Wiki
Jump to navigation Jump to search
Line 47: Line 47:
 
=== Vocabulary Recommendation(s) ===
 
=== Vocabulary Recommendation(s) ===
 
Create a concept domain called AdministrativeContactRoleType under RoleCode with the following definition:
 
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. 
+
Indicates the primary purpose or type of person intended to be reached using a set of contact information.
  
 
Examples:
 
Examples:
Line 58: Line 58:
  
 
Add the following new codes to the RoleCode code system under _AdministrativeContactRoleType:
 
Add the following new codes to the RoleCode code system under _AdministrativeContactRoleType:
 +
{|width=100% cellspacing=0 cellpadding=2 border=1
 +
|-
 +
|bgcolor="#aaaaff" align=center| '''Abbrev.'''
 +
|bgcolor="#bbbbff" align=center| '''Description'''
 +
|bgcolor="#aaaaff" align=center| '''# to Add'''
 +
|bgcolor="#aaaaff" align=center| '''# to Remove'''
 +
|bgcolor="#aaaaff" align=center| '''# 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''
 +
|-
 +
|}
  
 
+
Bind the new concept domain to the AdministrativeContactRoleType value set.
 
==Rationale==
 
==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.''
 
''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.''

Revision as of 17:37, 23 July 2009

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: PA-200908-01
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  


Summary of Vocabulary changes

Create a concept domain called AdministrativeContactRoleType and add additional concepts to existing code system.

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

RIM Recommendation(s)

Vocabulary Recommendation(s)

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.

Examples:

• Admitting

• Billing

• Test Results

Add the following new codes to the RoleCode code system under _AdministrativeContactRoleType:

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

Bind the new concept domain to the AdministrativeContactRoleType value set.

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