Incorporating component level details into NOTE table

Hi Everyone,
How are people handling component level details from pathology reports in the note table?
I realized our current ETL is creating a single note_id per component value. I am not sure if this is the most efficient method for organizing this information.
NOTE_LAB COMPONENTS

Hello @rkwpnw

For one pathology or other report/result/note in your data, you should combine the multiple source rows/lines into one NOTE row in OMOP. ETLing row for row leaves the data disconnected in OMOP since there isn’t a way to link the multiple rows. You could use Fact Relationship to link, but it is not necessary. Combining it is the most user friendly and accurate way to store the data in OMOP.

“Thanks, @MPhilofsky, that makes a lot of sense. I was wondering, though, when you combine the rows into one NOTE, how do you handle preserving the structure or headings from the original report? Do you embed those as plain text or use some kind of markup?”