World: r3wp

ok

>> caret: charset [ #"^^" ]
== make bitset! #{
0000000000000000000000400000000000000000000000000000000000000000
}

>> obx: {OBX|1|ST|Hb^ Hb:^L||135|g/L|120 - 155|N|||F^/}
== "OBX|1|ST|Hb Hb:^L||135|g/L|120 - 155|N|||F^/"

>> parse obx [ "OBX" "|" digits "|" "ST" "|" thru caret to end ]
** Script Error: Invalid argument: make bitset! #{
0000000000000000000000400000000000000000000000000000000000000000
}
** Where: halt-view

** Near: parse obx ["OBX" "|" digits "|" "ST" "|" thru caret to end]
>>

Is that with the caret as an escape char, or as a value?

that is thru with a charset. any caret

no, grrr, lack of smarter thru is annoying.

Because it looks like the carets in your data are registering as 
escape characters. That ^H is registering as a backspace character, 
not the sequence "^H".

any non-caret caret  ;?

It's ^spaceH

ok, parse enhancement proposal .. allow one to change the escape 
character.

If you loading your data like you do when you type it on the interpreter 
command line, carets are treated as escape characters. If you are 
getting it from the read command, they aren't.

that you have to escape all the ^ to ^^ in strings is true too, but 
not the error-reason. the rule should fail, not error.

the data is medical HL7 formatted data.

It's being read in from a file.

so, it shouldn't be escaped in the data itself.

So if you copy your test data to the clipboard, you would assign 
it to a variable like this:
obx: read clipboard://

If you are reading it from a file with the read or open functions, 
there is no escaping.

then it should be no problem. only when load sees it in strings. 
if you 'read it, no escaping is needed. and mold auto-escapes.

Ok, I am testing on the command line.  May be that is the problem.

Try reading from the clipboard directly like I suggested for that.

Note: The form native doesn't escape on output like mold does.

Oh wait, the error in his parse statement isn't because of escaping. 
It's the thru bitset that isn't supported. Try this:
caret: charset "^^"
non-caret: complement caret

parse obx ["OBX" "|" digits "|" "ST" "|" any non-caret caret to end 
]

does that return true ?

should work like thru.  "any non-caret" is like "to caret", then 
skipping it is like "thru caret". without caret it would go to end, 
and then the final skip fail.

>> obx: {OBX|1|ST|Hb^ Hb:^L||135|g/L|120 - 155|N|||F^/}
== "OBX|1|ST|Hb Hb:^L||135|g/L|120 - 155|N|||F^/"
>> caret: charset "^^"
== make bitset! #{
0000000000000000000000400000000000000000000000000000000000000000
}
>> non-caret: complement caret
== make bitset! #{
FFFFFFFFFFFFFFFFFFFFFFBFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
}
>> parse obx [ "OBX" copy test some non-caret caret to end ]
== false
>> test
== "|1|ST|Hb Hb:^L||135|g/L|120 - 155|N|||F^/"
>>

Yes, so it works

remember the "^" in your string are no "^", else they would be molded 
as "^^"

i would really get the data from outside. put them in a file and 
use obx: read %data.txt, or use clipboard.

ok, I'll give that a go later on.

obx: {OBX|1|ST|Hb^^ Hb:^^L||135|g/L|120 - 155|N|||F^^/}

(or copy from altme ;)

obx: {OBX|1|ST|Hb^ Hb:^L||135|g/L|120 - 155|N|||F^/}

Hu? Does altme escape too? there should be duble "^^" everywhere.

>> parse read clipboard:// [ copy test some non-caret caret to end 
]
== true
>> test
== "obx: {OBX|1|ST|Hb"

ok so that works.

Of course since you are looking for one character, you can use to 
or thru like this:
parse read clipboard:// [ copy test thru "^^" to end ]

Meoww, thats to simple for me.. good catch :)

well, if RT want to use Rebol in medical applications, they should 
look at making it easier to work with medical data !

OBX|1|ST|Hb^ Hb:^L||135|g/L|120 - 155|N|||F^/

Just using Altme as a clipboard.

Is there a standard we can read to get the syntax?

HL7 - yeah, hundreds of pages of specs.

Aaak.

http://www.hl7.org/

For instance, how many fields does that data you posted have? Are 
they seperated by | or is it a length thing?

I don't know .. I am just looking at sample data and trying to reverse 
engineer the format as I don't have time to read 100s of pages of 
specs.

What does the ^ mean in context?

but each OBX record is one blood result

It seems to be a delimiter to divide a record into parts

Really? By the format it looks like they are using | for that.