Difference between revisions of "Proposal: add InformRequestActType Concept Domain"
| Line 1: | Line 1: | ||
| − | + | '''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 | ||
| Line 10: | Line 9: | ||
|- | |- | ||
|} | |} | ||
| − | |||
| − | |||
== Summary Recommendation== | == Summary Recommendation== | ||
Revision as of 19:10, 19 February 2009
Proposal Name: New concept domain InformRequestActType and value set with example values
| Submitted by: Patrick Lyd | Revision date: February 19, 2009 |
| Submitted date: January 2009 WGM | Reommendation ID: CA-2009-04-4 |
Contents
Summary Recommendation
Create new concept domain InformRequestActType for use in the PR payload models for document routine.
Vocabulary Objects Change Summary
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 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.
Discussion
Had a discussion with Security WG – had no issues with naming of the concept domain as InformRequestActType.
Recommended Action Items
PA to implement recommendation
