Reminder: Create & find trunk-related issues here. Legacy Trac tickets are still available. Problems? Workflow feedback? Need a module project? Open a support ticket.

Form Entry Module

InfoPath schema incorrectly has HL7 sextuplets storing the selected name in both triplets.

Details

  • Type: Bug Bug
  • Status: Reopened Reopened
  • Priority: Must Must
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: OpenMRS 1.5
  • Component/s: None
  • Description:
    Hide

    The InfoPath schema should store HL7 sextuplets with
    concept_id^concept_name^99DCT^concept_name_id^selected_name^99NAM
    Example:
    5330^HIV STAGING - MINOR MUCOCUTANEOUS MANIFESTATIONS^99DCT^4544^MMM^99NAM\\\\
    Instead, the InfoPath HL7 schema is storing sextuplets with the selected name in both triplets.
    The schema is incorrectly represented as either:
    5330^MMM^99DCT^4544^MMM^99NAM
    or
    5330^HIV STAGING - MINOR MUCOCUTANEOUS MANIFESTATIONS^99DCT^2274^HIV STAGING - MINOR MUCOCUTANEOUS MANIFESTATIONS^99NAM

    Show
    The InfoPath schema should store HL7 sextuplets with
    concept_id^concept_name^99DCT^concept_name_id^selected_name^99NAM
    Example:
    5330^HIV STAGING - MINOR MUCOCUTANEOUS MANIFESTATIONS^99DCT^4544^MMM^99NAM\\\\ Instead, the InfoPath HL7 schema is storing sextuplets with the selected name in both triplets.
    The schema is incorrectly represented as either:
    5330^MMM^99DCT^4544^MMM^99NAM
    or
    5330^HIV STAGING - MINOR MUCOCUTANEOUS MANIFESTATIONS^99DCT^2274^HIV STAGING - MINOR MUCOCUTANEOUS MANIFESTATIONS^99NAM

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Ben Wolfe added a comment - 2009-07-30 15:49:28 EDT

Part of this was fixed in the formentry module in rev:9477 and rev:9478 and now a followup fix in rev:9537. This is fixed in formentry versions 4.1.2 and 3.6.9

Show
Ben Wolfe added a comment - 2009-07-30 15:49:28 EDT Part of this was fixed in the formentry module in rev:9477 and rev:9478 and now a followup fix in rev:9537. This is fixed in formentry versions 4.1.2 and 3.6.9
Hide
Permalink
Ada Yeung added a comment - 2010-08-31 05:43:27 EDT

The same problem has happened again in AMRS production. We got 951^VARICOSE LEG ULCERS^99DCT^951^VARICOSE LEG ULCERS^99NAM stored in obs_id=81118092.

Show
Ada Yeung added a comment - 2010-08-31 05:43:27 EDT The same problem has happened again in AMRS production. We got 951^VARICOSE LEG ULCERS^99DCT^951^VARICOSE LEG ULCERS^99NAM stored in obs_id=81118092.
Hide
Permalink
Nyoman Ribeka added a comment - 2010-08-31 06:08:26 EDT

This is just a coincidence that the concept_id = concept_name_id. The HL7 format seems to be still correct. I think you can close this issue.

Show
Nyoman Ribeka added a comment - 2010-08-31 06:08:26 EDT This is just a coincidence that the concept_id = concept_name_id. The HL7 format seems to be still correct. I think you can close this issue.
Hide
Permalink
Ada Yeung added a comment - 2010-08-31 07:32:42 EDT

It is not displaying correctly on the webapp. I will file for a new ticket instead.

Show
Ada Yeung added a comment - 2010-08-31 07:32:42 EDT It is not displaying correctly on the webapp. I will file for a new ticket instead.

People

Dates

  • Created:
    2009-06-26 16:08:25 EDT
    Updated:
    Tuesday 07:33:29 EDT
    Resolved:
    2010-07-01 22:44:19 EDT
Atlassian JIRA (v4.1.1#522) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for OpenMRS. Try JIRA - bug tracking software for your team.