Difference between revisions of "Proposal: add InformRequestActType Concept Domain"

From HL7Wiki
Jump to navigation Jump to search
 
(19 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
Return to [[Patient_Administration]]
 +
 
'''Proposal Name: New concept domain InformRequestActType and value set with example values'''
 
'''Proposal Name: New concept domain InformRequestActType and value set with example values'''
  
 
{|width=100% cellspacing=0 cellpadding=2 border=1
 
{|width=100% cellspacing=0 cellpadding=2 border=1
 
|| '''Submitted by:''' Patrick Loyd
 
|| '''Submitted by:''' Patrick Loyd
|| '''Revision date:''' February 19, 2009
+
|| '''Revision date:''' February 25, 2009
 
|-
 
|-
 
|| '''Submitted date:''' January 2009 WGM
 
|| '''Submitted date:''' January 2009 WGM
|| '''Reommendation ID:''' CA-2009-04-4
+
|| '''Recommendation ID:''' CA-2009-04-4
 
|-
 
|-
 
|}
 
|}
Line 12: Line 14:
 
Vocabulary Object Change Summary
 
Vocabulary Object Change Summary
 
{|width=100% cellspacing=0 cellpadding=2 border=1
 
{|width=100% cellspacing=0 cellpadding=2 border=1
|| '''Abbrev'''
+
|| '''Abbrev.'''
 
|| '''Description:'''
 
|| '''Description:'''
 
|| '''# to add:'''
 
|| '''# to add:'''
Line 20: Line 22:
 
|| D
 
|| D
 
|| Concept Domains
 
|| Concept Domains
 +
|| 1
 
||
 
||
 +
||
 +
|-
 +
|| S
 +
|| Code Systems
 +
||
 +
||
 +
||
 +
|-
 +
|| C
 +
|| Concept Codes in a Code System
 +
|| 4
 +
||
 +
||
 +
|-
 +
|| V
 +
|| Value Set
 +
||
 +
||
 +
||
 +
|-
 +
|| B
 +
|| Context Binding
 
||
 
||
 
||
 
||
Line 28: Line 53:
  
 
== Summary Recommendation==
 
== Summary Recommendation==
Create new concept domain InformRequestActType for use in the PR payload models for document routine.
+
Create new concept domain InformRequestActType for use in the Provider Registry (PR) payload models for document routing (see InformRequest class).
 
 
== Vocabulary Objects Change Summary==
 
  
 
== Issue ==
 
== Issue ==
Line 45: Line 68:
  
  
Concept Domain definition: Codes which specify a document type for which a provider is requesting routing of that document type from the specific service delivery location to them.  Examples could include Diagnostic Image Interpretations, Lab Test Results, Electro-Cardiogram Reports.
+
Concept Domain definition: Codes which specify an information type for which a provider is requesting routing of health information.  This could include messaging of results or documents especially in the context of a specific service delivery location.  Examples include documents from the specific service delivery location to them.  Examples could include Diagnostic Image Interpretations, Lab Test Results, Electro-Cardiogram Reports.
  
 
== Discussion ==
 
== Discussion ==
Had a discussion with Security WG – had no issues with naming of the concept domain as InformRequestActType.
+
It was confirmed with Security WG – that from a security perspective, there are no issues with naming of the concept domain as InformRequestActType.
 +
 
 +
 
 +
This is different from documentType concepts as this is within the InformRequest class which purpose is to indicate what type of health information is being routed from a specific service delivery location to them. The documentType concept domain is for general description of different types of documents that exist and health information may not necessary be documents.
  
 
== Recommended Action Items ==
 
== Recommended Action Items ==

Latest revision as of 19:30, 2 March 2009

Return to Patient_Administration

Proposal Name: New concept domain InformRequestActType and value set with example values

Submitted by: Patrick Loyd Revision date: February 25, 2009
Submitted date: January 2009 WGM Recommendation ID: CA-2009-04-4

Vocabulary Object Change Summary

Abbrev. Description: # to add: # to remove: # to change:
D Concept Domains 1
S Code Systems
C Concept Codes in a Code System 4
V Value Set
B Context Binding

Summary Recommendation

Create new concept domain InformRequestActType for use in the Provider Registry (PR) payload models for document routing (see InformRequest class).

Issue

Artifacts in the ballot use generic ActCode concept domain (which is retired). Seek to define a new concept domain.

Current State

PR Models which contain the InformRequest clone class, currently bind the code attribute to the ActCode concept domain, which was retired (removed during November 2008 Harmonization). There is currently no other specific concept domain which seems appropriate for usage with InformRequest.code.

Rationale

See Issue

Recommendation Details

Create a new concept domain InformRequestActType as a parent concept domain and use for binding InformRequest.code.


Concept Domain definition: Codes which specify an information type for which a provider is requesting routing of health information. This could include messaging of results or documents especially in the context of a specific service delivery location. Examples include documents from the specific service delivery location to them. Examples could include Diagnostic Image Interpretations, Lab Test Results, Electro-Cardiogram Reports.

Discussion

It was confirmed with Security WG – that from a security perspective, there are no issues with naming of the concept domain as InformRequestActType.


This is different from documentType concepts as this is within the InformRequest class which purpose is to indicate what type of health information is being routed from a specific service delivery location to them. The documentType concept domain is for general description of different types of documents that exist and health information may not necessary be documents.

Recommended Action Items

PA to implement recommendation

Resolution