René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"OBX-5 is valued, but OBX-2 is not. A datatype for OBX-5 must be specified using OBX-2.","articleBody":"it appears that HAPI has a valid solution for this exception\n\nThe HAPI Parser may be configured using a ParserConfiguration object.\n\nThe ParserConfiguration is a bean which sets and retrieves parser configuration properties and may be shared among multiple parser instances.\n\nDefault behaviour for OBX-2\nIn a normal OBX (Observation) segment, OBX-2 provides the datatype to be applied to OBX-5. So, for instance if an OBX repetition was conveying a timestamp (TS), it might look like:\n\nOBX||TS|||200901011259\nIf the OBX-2 value is missing (which sometimes happens because of a misbehaving sending system), you may see an error such as \"OBX-5 is valued, but OBX-2 is not. A datatype for OBX-5 must be specified using OBX-2\".\n\nIn this case, you may specify that HAPI should use a default type when none is found by specifying a default OBX-2 type:\n\nparser.getParserConfiguration().setDefaultObx2Type(\"ST\");\nORU_R01 parsedMessage = (ORU_R01)parser.parse(someInvalidMessage);\nIf the OBX-2 value is invalid, meaning that it has a value but that value is not a valid HL7 datatype (e.g. \"String\" instead of \"ST\"), you may specify a default type to assume if the OBX-2 value can not be understood.\n\nparser.getParserConfiguration().setInvalidObx2Type(\"ST\");\nORU_R01 parsedMessage = (ORU_R01)parser.parse(someInvalidMessage);\nSee the JavaDoc for examples.\n\nbut can this be done in nHAPI ? \n\nRegards,\n-Alex\n","author":{"url":"https://github.com/AlexFJaxFL","@type":"Person","name":"AlexFJaxFL"},"datePublished":"2016-10-20T20:49:19.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/63/nHapi/issues/63"}