not all co-constrints require an OBX-5 definition

afrold / igamt

Implementation Guide Authoring and Management Tool

3 stars 2 forks source link

not all co-constrints require an OBX-5 definition #2500

Open csnewman88 opened 7 years ago

csnewman88 commented 7 years ago

When the data type for a line in a co-constraints table is not a coded data type, there is no need for an OBX-5 value or valueset. At one point, we just to be able to designate this as "n/a" for rows using DT, TX and other non-coded data types. Not sure what happened to that functionality, but we need something similar.

Jungyubw commented 7 years ago

fixed

smartinez290 commented 7 years ago

The issue is still there.

smartinez290 commented 6 years ago

NO sure this issue is fixed. Also, the column calls fro a v/s but the entry indicates vs or value.

Jungyubw commented 6 years ago

@smartinez290 or @robnist

Do we need to disable to edit OBX-5 if datatype is not coded element?