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

Difference between revisions of "PHER-CR02-Change Entity name cardinality in PHE CMETs"

From HL7Wiki
Jump to navigation Jump to search
(New page: {{PHER Open Change Requests}} Return to PHER page; Return to [[:category:Change Requests for PHER Standards|Change Requests for ...)
 
 
Line 1: Line 1:
 
{{PHER Open Change Requests}}
 
{{PHER Open Change Requests}}
 +
[[Category:PHER-CMET Change Requests]]
  
 
Return to [[Public Health and Emergency Response work group (PHER)|PHER]] page; Return to [[:category:Change Requests for PHER Standards|Change Requests for PHER Standards]] page.
 
Return to [[Public Health and Emergency Response work group (PHER)|PHER]] page; Return to [[:category:Change Requests for PHER Standards|Change Requests for PHER Standards]] page.

Latest revision as of 17:02, 22 March 2010


Return to PHER page; Return to Change Requests for PHER Standards page. (An announcement of this proposal must be submitted to the PHER list to be formally submitted.)

Submitted by: Austin Kreisler (on behalf of Clinical Statement) Revision date: <<Revision Date>>
Submitted date: 4/10/2009 Change request ID: PHER-CR02
Standard: PHER CMET Release 10 Artifact ID, Name: E_PublicHealthEntity universal(COCT_RM840000UV)

Issue

The E_PublicHealthEntity universal CMET allows only a single name in the Enity class.

Recommendation

  • In the E_PublicHealthEntity universal CMET, change the cardinality of the Entity.name attribute from 0..1 to 0..* and change the data type from ST to BAG<ST> or BAG<TN>.
  • Make the same change in other relevant PHE based CMETs.
  • Consider makeing a similar change to the EntityGroup class in the PHE models. Groups can also have multiple names.

Rationale

In general, entities may have more than a single name associated with them. Other entity classes in the same model allow multiple names, the Entity class in the model should be consistent with this approach also.

Discussion

Since this is a relaxation of constraints, it is considered a backward compatible change by the rules for V3 backwards compatibility.

Recommended Action Items

Resolution

(Resolution is to be recorded here and in the referenced minutes, which are the authoritative source of resolution).