PA Items - 2006Sep

From HL7Wiki
Jump to navigation Jump to search

The foolowing reconciliation items were forwarded from PA after ballot 2006Sep.

Return to Referred Publishing Items

Content from Reconciliation Spreadsheet
Item ID Source Artifact Level Issue Proposed Disposition
PAPA-2 Freida Hall PRPA_IN101301 A-S The Publication Database only allows selecting Send Message Payload transmission wrapper MCCI_MT000100 but the Transmission Infrastructure ballot states that MCCI_MT000100UV01 "is for backwards compatibility only. The use of this artifact is discouraged. It will be removed from the standard at some point in the future" and advises use of MCCI_MT002100

This applies to all PA interactions using Send Message Payload wrapper.

Recommended Resolution:

This appears to be a shortcoming of the PubDb. It should permit selection of all defined wrappers, whether Normative or not. This allows new material to be developed using new wrappers that are also in development.

PAPA-3 Freida Hall PRPA_IN101312 A-S The Publication Database only allows selecting Application Level Acknowledgement transmission wrapper MCCI_MT000300 but the Transmission Infrastructure ballot states that MCCI_MT000300UV01 "is for backwards compatibility only. The use of this artifact is discouraged. It will be removed from the standard at some point in the future" and advises use of MCCI_MT002300

This applies to all PA interactions using Application Level Acknowledgement wrapper.

Recommended Resolution:

This appears to be a shortcoming of the PubDb. It should permit selection of all defined wrappers, whether Normative or not. This allows new material to be developed using new wrappers that are also in development.

PAPA-4 Freida Hall PRPA_HD101301 A-S Change description for Person.desc attribute in this and all PA HMD's PA noted: TC agrees that description should agree with RIM description (suggested wording does not match current RIM description). TC also forwards a request to Publishing for Table View and Excel View to default to description from parent model where a TC has not entered a revised description.

M&M in discussion has said that it does not wish Table Views and Excel View to be populated with RIM descriptions when the committee has not edited them.

Recommend that Publishing suggest to Tooling that the RIM definitions be made available in the documentation tool (Visio RMIM designer) so that developing committee can copy and amend the RIM description, if desired.

PA-11 June Rosploch A-T In most places where an identifier is a concatenated set of words, “camel-case” (upper case for 1st letter of each word) is used to improve readability, for example “lengthOfStayQuantity”. However in section 2, camel-case is not used for Structured Sort Name “Identifiedperson” and in section 3, same applies to Structured Sort Name “Patientlivingsubject”. Recommended finding:

Structured sort names are intended solely for machine processing, NOT for human reading. Therefore camel case has no function. These names should NOT appear anywhere in the person-readable content. If they do, please advise us where.