RPT

Repeat Pattern

Composite
FHIR:Timing
Definition: The repeat pattern data type should be used where it is necessary to define the frequency at which an event is to take place. This data type provides a way to define repeat pattern codes "on the fly". The repeat pattern code is equivalent to the TQ data type, component 2, sub-component 1 (repeat pattern). The additional components define the meaning of the repeat pattern code. Components 2 - 10 are used to define relatively simple repeat patterns. Component 11 is provided to define complex repeat patterns. This data type forms a bridge between the 2.x Repeat Pattern concept from Quantity/Timing, and the Version 3.0 GTS General Timing Specification. Component 1 is the 2.x concept of repeat pattern. Components 2-7 are derived from the version 3.0 data type PIVL. Components 8-10 are derived from the version 3.0 EIVL data type. If a repeat pattern cannot be defined using components 2-10, then component 11, General Timing Specification is provided. This allows the full literal form of the version 3.0 GTS to be specified.

When using the RPT, if an application doesn't recognize the code in component 1, then it may attempt to determine the appropriate frequency using the remaining components. If the application does recognize the code in component 1, the application is not required to determine the frequency from the remaining components.

3Conf Length→ 10=
4Conf Length→ 10=
5Conf Length→ 10=
9Conf Length→ 10=
11
Comp#FHIR
1786--RRPT.1Repeat Pattern Code
27872-ORPT.2Calendar Alignment-
3788-10=O-RPT.3Phase Range Begin Value
4789-10=O-RPT.4Phase Range End Value
5790-10=O-RPT.5Period Quantity
6791--C-RPT.6Period Units
77921-ORPT.7Institution Specified Time-
87933-ORPT.8Event
9794-10=O-RPT.9Event Offset Quantity
10795--C-RPT.10Event Offset Units-
11796--O-RPT.11General Timing Specification-
Used In Segment Fields