World: r3wp

Ok, let me rephrase that .. sure it's possible, but I can imagine 
it would be quite complicated

now was that a question of the "can you give me the solution" kind?

actually it can be done quite simply... depends on the headers themselves...

It's a little complicated because the headers can have spaces in 
them.

spaces add no complication to the system, as long as the headers 
can be identified without doubt.

so the rule is :

headers start on new line, stop at first ":" 
all the rest is content?

now if you have a rule
copy text [ to "a:" | to "b:" .... ] 

but if b: occurs before a: in the text, then you will include a header 
in copied text

forget to and thru... they are not proper parsing.

yes, headers start on a newline and terminate in ":"

and there can be no ":" within the content?

No, there can be a ":" in the content

but you know what the headers are ... so that's not a big problem.

ok, so they are explicit... then its very easy.

can you give the name of some the headers... or an example.... so 
far it looks like a really simple rule to me.

eg. "social history:"

and you want the output in neat blocks I guess.

give me 1 minute

so I guess we can masks for each possible header

^/social history:

or apply the rule recursively until it is false

I can assume it starts at a header?

might be leading newlines

or white spaces

ok, but no content or stray letters?

shouldn't be yet.

So, I am trying to create an object from a semi structured document 
where the object elements are in any order or missing.

almost done...

ok, so we replace the spaces in the headers by "-"  and create an 
object out of all the code...

all the content... rather

I guess I can do it without using parse .. just replace all the headers 
with a mark, that allows me to split off all the sections, and then 
i can match the sections with all the section headers.

I'm almost done... I like these little parse tests.. It keeps my 
mind sharp on using parse  ;-)

But I don't need parse!  :)

are you asleep ? :-)

its working but its skipping the first tag for some reason.

Huh?  just dozing ...

aaahh there is no newline on the start of the text hehehe

graham, obviously the simplest solution is to read/lines.

read/lines doesn't work on text in memory AFAIK

and just see if the line starts with one of the headers.

what's the content look like ?
Can't you just post an example Graham ?

parse text "^/"

CC:
Patient complains of sore throat.

HPI:
ONSET: Sudden, TIMING: Constant, DURATION: 3 days

INTENSITY: Moderate, QUALITY: Burning, MODIFYING FACTORS: head position

CURRENT MEDICATIONS:
TYLENOL W/ CODEINE NO. 3 300MG;30MG 1-2 po q 4-6 hrs prn "pain"
cyclobenzaprine Oral Tablet 10 MG 1 tab po TID prn "muscle spasm"

MEDICAL HISTORY:
Rheumatic heart disease, unspec. 391.9
Eczema, atopic dermatitis 691.8
dyslipidemia

ALLERGIES:
Penicillin - allergy: Allergy
Penicillin - allergy: Allergy
Penicillin - anaphylactic reaction
lovastatin - allergy: allergic
macrodantin - 1 po BID

SURGERIES:


HOSPITALIZATIONS:


FAMILY HISTORY:


SOCIAL HISTORY:


ROS:


VITALS:


EXAMINATION:
General: Appears non-toxic

HEENT: TONSILS hypertrophic, and erythematous. MOUTH buccal mucosa, 
moist. PHARYNX indurated, and angry. NOSE turbinates, with no obstuction.

Neck: NECK Supple, with no lymphadenopathy, thyromegaly, or masses.
CVS: HEART RRR s M
Chest: ANTERIOR LUNGS clear bilat


ASSESSMENTS:
391.9 Rheumatic heart disease, unspec.


TREATMENT:


PROCEDURES:


IMMUNIZATIONS:


IMAGING:


LABORATORY:


EDUCATION:
None.

REFERRALS:
Non contributory.

FOLLOWUP:


SUPERBILL:

That was sent to me today as an example

Hmm...

implementing later solution... this is easier

here you go  :-)


data: {CC:
Patient complains of sore throat.

HPI:
ONSET: Sudden, TIMING: Constant, DURATION: 3 days

INTENSITY: Moderate, QUALITY: Burning, MODIFYING FACTORS: head position

CURRENT MEDICATIONS:
TYLENOL W/ CODEINE NO. 3 300MG;30MG 1-2 po q 4-6 hrs prn "pain"
cyclobenzaprine Oral Tablet 10 MG 1 tab po TID prn "muscle spasm"

MEDICAL HISTORY:
Rheumatic heart disease, unspec. 391.9
Eczema, atopic dermatitis 691.8
dyslipidemia

ALLERGIES:
Penicillin - allergy: Allergy
Penicillin - allergy: Allergy
Penicillin - anaphylactic reaction
lovastatin - allergy: allergic
macrodantin - 1 po BID

SURGERIES:
}

data: parse/all data "^/"


header-lbl: ["CC" | "HPI" | "ONSET" | "INTENSITY" |"CURRENT MEDICATIONS" 
| "MEDICAL HISTORY" | "ALLERGIES" | "SURGERIES"]

spec: []
foreach line data [
	unless parse/all line [
		copy hdr [header-lbl ":"]
		here:
		(

   append spec to-set-word head remove back tail replace/all hdr " " 
   "-"
			append spec copy/part here tail line
		)
	][
	
		if string? item: last spec [
			append item line
		]
	]

]

probe context spec

ok for you?

Assuming SRC: contains the source text, it seems to work too:

header-char: complement charset "^/:"
EOL2: rejoin [newline newline]
parse/all src [
	some [
		some [pos: #" " (change pos #"-") | header-char]
		#":" pos: newline (change/part pos " {" 1)
		[to EOL2 | to end] pos: (change pos "} ") skip skip
	]
]
probe construct to block! src

Yes ... but I'm going to have to study Steeve's

to see why it doesn't work yet