Field note_nlp."offset" should be integer, not varchar
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.1k
- Forks
- 508
- Avg merge
- 1h 30m
- Merged PRs (30d)
- 3
Description
From the documentation
Character offset of the extracted term in the input note
I am assuming that in this context this field is expected to contain a numeric value: index position of start character of the extracted token (note_nlp.lexical_variant) in the string of the entire text (note.note_text).
For instance, if the note text is "Diagnosed with eczema", value of note_nlp.lexical_variant would be eczema and value of note_nlp."offset" would be 15.
My assumption is that the purpose of this field is to specify which occurence of the same literal token is referred to. So it should just be an integer, with no extra information.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the note_nlp field definition in the linked CDM 5.4 documentation and compare its declared type with the repository’s corresponding definition and DDLs. Confirm the intended representation of offset, then update every affected schema reference and verify that the documentation and generated definitions agree.
Written by the indexing model from the issue text.
Assessment
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100